CSS in widget

Similar Questions

• How is it difficult to update a Web site with mobile platforms, but also office?

  I just updated my CC from Adobe for photographers to the full version of CC for most to get Muse. I thought it was completely adaptable to mobile devices. Now I find that that is not necessarily true. It is true that I have to run three different platforms for mobile comparability? If this is true can I update all three, each time I change or add to my Web site? How is it hard to do this?

  Also, I read somewhere that if it is not hosted at Adobe, some of the Add-ons like forms and articles may not work. Is this correct?

  Thanks for any help,

  Linda

  Cross-platform support depends on what models / themes you use and their associated CSS and widgets. Not everything works everywhere and it is something you have to live with, has been for example support for JavaScript on mobile devices is usually a pain in the rear. Otherwise you get what you pay for - if you need more forms or other items, you will need to spend your limited options included in MU and look around. But I really don't see the issue. You can have anything from blogs to forums for free these days, you might just live with the fact that then you would not at all use Muse to manage and add content.

  Mylenium

• delayed popup

  delayed popup. I design slideshow full screen and you want to display text/image about 3-5 seconds after the start of the slide show. (about 3 slides) Example scroll down / left directions to continue. would he appear low center and center left/right. This is possible in Css or widget. Thank you

  You can use the composition and create a pop-up where auto playback can be configured with time delay, so the recovery time can be configured.

  Thank you

  Sanjit

• Inline CSS of my widget ECWID adds extra CSS, How Do I Get Rid Of It?

  My site is www.hershbergerfurniture.com, I use ECWID to the store and pulling on the site of muse. Everything works fine, however, I get a weird text in front of the "Buy now" button, it looks like this:

  

  Now, when I inspect it, I see that it comes from here:

  

  When I delete the 'content' attribute, the text disappears.

  My question is, how in the world actually delete it from my CSS Web site?

  When I inspect in firefox, it says that the code is inline:48

  

  I know how to edit and mess with CSS, I do it all the time. However, in this case, I don't really know how the hell to find this code string in files and how to fix.

  Help, please.

  It's not CSS, this is a reference to variable used in the widget code. It is likely that the name has a typo in; If there is no matching name, just Muse puts the parameters name verbatim, as it has here.

  Drop the developer an email asking to be fixed.

  I hope this helps.

  David

  http://creativemuse.co

• Question for Hiroto - css user

  I redesigned the css for the Spanish and Portuguese CSA web site.  I modified your css.

  Here's what I came with:

  Re: Style sheet for Japanese, Korean, Spanish and Portuguese CSA sites user

  I have two questions:

  (1) I want the 'P' in order to act as 'R' when the window is made narrower.  See this web page.  Make the windows smaller and larger to see 'P' and 'R' in action.

  https://communities.Apple.com/pt/thread/4601

  When I do the narrow window the letter P [issue] is scrolled off the right but the letter R [answer] does not work.

  P's off to the left

  

  P is visible

  

  (2)

  You remember what ASC Web page the effects of this code?  I couldn't identify a use of this code.

  What is "Community list table"? [jive now decides he wants to put a lot of spaces in this.]  who know why]

  
  /* ------------------ 
  
    
  Treatment for narrow window 
  
    
  Method 1 (minimum optimisation) 
  
    
  Adjust community list table's shift and margin to maximize its width. 
  
  */                                                                 
  /* v0.43 */  
  
  /* ------------------ (currently commented out) 
  
  .j-layout-sl.j-browse-places .j-column-wrap-l { margin-left: -166px !important; } 
  
  .j-layout-sl.j-browse-places .j-column-l 
  { margin-left: 166px !important; } 
  
  .j-layout-sl.j-browse-places .j-column-s 
  { width: 166px !important; } 
  
  ------------------ */  
  
  /* ------------------ 
  
     
  Treatment for narrow window 
  
     
  Method 2 (more beneficial to narrow window but has disadvantage for wide window) 
  
       
  
     
  Let community list table have full width but not exceed 1019px to make room for 
  
     
  sidebar ui (filters & actions).  If window is wide enough (>=1265px), sidebar ui 
  
     
  is displayed next to community list table, otherwise it is displayed below or 
  
     
  above it (depending upon its document tree order). 
  
       
  
     
  * sidebar width (constant)
  = 166px 
  
     
  * community table max width   = 1019px 
  
     
  * canvas margin-left     
  = 40px 
  
     
  * canvas margin-right    
  = 40px 
  
     
  --------------------------------------- 
  
     
  * total                  
  = 1265px 
  
  */                                                                   
  /* v0.5 */  
  
  /* ------------------ (currently active) */  
  
  .j-layout-sl.j-browse-places .j-column-wrap-l { max-width: 1019px !important; }  
  
  .j-layout-sl.j-browse-places .j-column-wrap-l { margin-left: 0px !important; }  
  
  .j-layout-sl.j-browse-places .j-column-l 
  { margin-left: 0px !important; }  
  
  .j-layout-sl.j-browse-places .j-column-l 
  { padding-left: 0px !important; }  
  
  .j-layout-sl.j-browse-places .j-column-s 
  { width: 166px !important;  }      
  
  /* ------------------ */  
  
     
  

  Hello

  Well, it took me some time to investigate the new presentation of 2016-06 of the ASC (Japanese, etc). It's really annoying...

  You can find my current project CSS below. For better maintainablility, I made new CSS file derived from the previous one for 2014-06 format. Section of the DISPLAY OF THE WIRE CONTENT has been significantly redesigned. It may contain useless residues of the previous, because I have not yet cleaned up seriously.

  Moreover, the Q brand in question is placed in a strange way, using the negative zone offset (left:-60px banner), which would be the reason why it behaves well in your settings.

  Relevant rules in original CSS:

  .j-thread #body-apple .j-thread-post section.j-original-message h1 {
      max-width: 860px;
      margin: 0px auto 30px;  /* <-- left margin is auto, which may be problematic in variable width environment */
  }
  .j-thread .jive-content .j-thread-post section.j-original-message h1 .q-marker {
      position: absolute;
      top: 0px;
      left: -60px;            /* <-- negative box offset for left side */
      font-size: 55px;
      font-weight: 200;
      line-height: 1em;
  }
  

  which I adjusted it as follows:

  .j-thread-post section.j-original-message h1 {
      max-width: inherit !important;;
      margin: 0px 60px 20px 60px !important;;
  }
  .j-original-message h1 .q-marker {
      left: -60px !important;
      font-size: 32px !important;
  }
  

  ---

  Here's my project. Please feel free to change, adapt, and reuse what you see fit.

  /*
      custom styles for Apple Support Communities board system introduced in 2016-06 (v0.10d)
     
      written by Hiroto, 2016-06
  */
  @-moz-document
      domain(communities.apple.com),
      domain(discussionsjapan.apple.com),
      domain(discussionskorea.apple.com)
  {
      /* ------------------------------------------------------------------------------------------------
          BODY
      */
      body.j-body-welome,             /* Welcome */
      body.j-body-place,              /* Community */
      body.j-body-yourwork,           /* Content */
      body.j-body-home,               /* Activity */
      body.j-body-yourconnections,    /* People */
      body.j-body-preferences,        /* Preferences */
      body.jive-body-content,         /* Thread */
      body.jive-body-search,          /* Search */
      body.jive-view-profile          /* Profile */
      {                                                                              
          background: white !important;
      }
      body {
          background: white;
          min-width: 0px !important;
      }
      #body-apple {
          width: 100% !important;
          min-width: 0px !important;
      }
      #globalheader { display: none !important; }                                    
      #global-nav-wrapper {display: none !important; }                               
      #globalfooter,
      #globaldisclaimer { width: 80% !important; }                                    
  
      /* ------------------------------------------------------------------------------------------------
          TEXT
      */
      body {                                                                                  /* NEW */
          font-size: 16px !important;
          font-weight: 400 !important;
          line-height: 1.25 !important;
      }
     
      body * {                                                                                /* NEW */
          /* font-size: inherit !important; */
          font-weight: inherit !important;
          line-height: inherit !important;
      }
  
      /* ------------------------------------------------------------------------------------------------
          ASC HEADER, FOOTER AREA
      */
      #j-header,
      #j-compact-header,
      #j-footer { width: 100% !important; }
     
      /* navigation header (Apple Support Communities ...) */
      #j-header-wrap {
          padding: 0px 40px !important;
          margin: 0px 0px 15px !important;
      }
      #j-globalNav-bg {
          padding: 0pX !important;
          margin: 0px !important;
          width: auto !important;                                                             /* NEW */
      }
      #j-satNav { overflow: visible !important; }
  
      #j-header-wrap { margin-bottom: 50px !important; }                                      /* NEW */
      #apple-full-header { margin: 10px 0px 0px !important; }                                 /* NEW */
      #second-row {                                                                           /* NEW */
          padding-top: 25px !important;
          height: 30px !important;
      }
  
      #jive-alert {                                                                           /* NEW */
          width: auto !important;
          max-width: inherit !important;
          margin: -20px 40px 10px !important;
      }
      .j-thread #jive-alert {                                                                 /* NEW */
          margin: -50px 40px 10px !important;
      }
      .jive-body-formpage.j-thread #jive-alert {                                              /* NEW */
          margin: -30px 40px 10px !important;
      }
      #jive-breadcrumb {                                                                      /* NEW */
          width: auto !important;
          margin-right: 40px !important;
          position: relative !important;
      }
      .j-js-footer-wrap {                                                                     /* NEW */
          width: auto !important;
          min-width: 0px !important;
      }
      footer#j-footer {                                                                       /* NEW */
          width: auto !important;
          min-width: 0px !important;
      }
  
      /* ------------------------------------------------------------------------------------------------
          ASC TOP PAGE
      */
      .j-body-welcome #jive-alert { margin: 0px 40px !important; }
      .j-body-welcome .hero-container img { width: auto !important; }
      .j-body-welcome.j-body-home [id|=jive-widgetframe] > .content-large {
          text-align: center !important;
          overflow-x: auto !important;
          overflow-y: hidden !important;
      }
      .apple-communities {
          display: inline-block !important;
          width: auto !important;
          text-align: left !important;
      }
  
      /* ------------------------------------------------------------------------------------------------
          THREAD LIST BROWSER
      */
  
      /* ------------------
          community overview
      */                                                                                      /* NEW */
      .category-latest .category-latest-container .category-latest-row {
          margin: 0px !important;
          padding: 5px 0px !important;
      }
      .category-latest .category-latest-container .category-latest-row .discussion-metadata {
          margin: 5px 0px !important;
      }
      .category-latest .category-latest-container .category-latest-row .discussion-title a {
          font-size: 110% !important;
          font-weight: 500 !important;
          color: rgb(0, 136, 204) !important;
      }
      .category-latest .category-latest-container .category-latest-row:nth-child(odd) {
          background: rgb(247, 247, 247) !important;
      }
      .category-latest .category-latest-container .category-latest-row .read-full {
          display: none !important;
      }
     
      .apple-space-overview #body-apple .list-page .ask-a-question-sidebar {
          margin: 0px 70px 10px 0px !important;
      }
      .apple-space-overview #body-apple .list-page .ask-a-question-sidebar .ask-a-question-space-icon {
          width: 128px !important;
          height: 128px !important;
      }
      .apple-space-overview #body-apple .list-page .ask-a-question-wrapper .community-siblings {
          padding: 5px 0px !important;
          font-size: 20px !important;
      }
      /* ------------------ */
      
  
      /* show author name in 'Latest activity' column in detailed list view of threads */
      td.j-td-date > span { display : inherit !important; }
  
      /* main section */
      #j-main { padding: 0px !important; }
  
      /* table cell title */
      .jive-table td.jive-table-cell-title { padding: 5px !important; }
         
      /* thread list view column widths */                                           
      .j-browse-details .j-td-title { max-width: none !important; }
      .j-browse-details .j-td-date {
          width: auto !important;
          max-width: 20% !important;
      }
      
  
      /* ------------------
          Hide Like and Bookmark columns in thread list view.
      */                                                                             
      /* ------------------ (currently commented out)
      .j-browse-details .j-td-likes,
      .j-browse-details .j-td-bookmarks { display: none !important; }
      .j-browse-details > table.j-browse-list > thead.j-rc4 > tr > th + th,
      .j-browse-details > table.j-browse-list > thead.j-rc4 > tr > th + th + th { display: none !important; }
      .j-browse-details > table.j-browse-list > thead.j-rc4 > tr > th + th + th + th { display: table-cell !important; }
      ------------------ */
  
      /* user name link */
      .jive-username-link { text-transform: none !important; }                        
  
      /* threads list view table tr td  */
      .j-browse-details-tbody tr td { padding: 2px !important; }                              /* CHANGED */
  
      /* threads list view left most icon */
      .j-browse-details-tbody .j-td-icon { padding: 0px 6px 0px !important; }                 /* NEW */
     
      /* communities list view table tr td */
      .jive-communities-listing table tr td { padding: 5px !important; }
     
      /* thumbnails view width */
      .j-browse-content .j-thumb-view,
      .j-browse-places .j-browse-thumbnails,
      .j-browse-people .j-browse-thumbnails { width: 100% !important; }
     
      /* thumbnail view list item margin */                                          
      .j-browse-content .j-thumb-view > li,
      .j-browse-places .j-browse-thumbnails > li { margin-right: 20px !important; }
     
      /* thumbnail view article font size */                                                  /* NEW */
      .j-thumb article { font-size: inherit !important; }
     
      /* thunbnail view article header height */                                              /* NEW */
      .j-content-thumb header { height: 22px !important; }
  
      /* thumbnail view article height */                                                     /* NEW */
      .j-browse-content .j-content-thumb article { height: 120px !important; }
     
      /* thumbnail view footer */                                                             /* NEW */
      .j-browse-content .j-content-thumb.j-thumb footer { padding: 4px 0px 0px !important; }  
  
     
      /* social actions row */
      .apple-social-actions-wrapper { margin-right: 0px !important; }
      .j-thread .j-social-actions { margin-right: 40px !important; }
  
      /* apple header, subheader row ("Find helpful contents..." etc )*/             
      #apple-full-subheader,
      #apple-activity-subheader {
          padding: 0px 40px 15px !important;
          margin-bottom: 15px !important;
      }
      #apple-full-header h2,
      #apple-activity-header h2 { padding: 0px 40px !important; }
  
      /* page header */
      .j-body-place #jive-body > header.j-page-header {
          margin-left: 40px !important;
          margin-right: 40px !important;
          width: auto !important;
      }
     
      /* pagenation */                                                                        /* NEW */
      .j-pagination-prevnext > .j-pagination-prev,
      .j-pagination-prevnext > .j-pagination-next { font-size: 0px !important; } 
     
     
      /* browser filter row */
      #j-browse-filters { margin-bottom: 5px !important; }
  
      /* browser controls row */
      .j-type-row { margin-bottom: 0px !important; }
  
      /* browser controls content types (All Contents|User Tips|Discussions) width */
      #js-browse-controls .j-type-row .j-content-types { width: 90% !important; }
     
      /* browser controls view toggle (Thumbnails|Details) width */
      #js-browse-controls #j-item-view-toggle {
          width: 10% !important;
          display: table !important;
      }
  
      /* content filter row (All|Open|Answered|Threads) */
      .j-content-filter {
          background: white !important;
          margin-bottom: 10px !important;
      }  
     
      /* container canvas */
      .j-contained {
          margin-left: 40px !important;
          margin-right: 40px !important;
      }
  
      /* category filter bar */
      .jive-content-filter {
          left: 0px !important;
          width: 80% !important;
      }
      .touchcarousel-wrapper { width: 100% !important; }
      .touchcarousel .tc-paging-container { width: 90% !important; }                  
  
      /* more search results available */
      #j-more-search-results-available { padding: 10px !important; }
     
      /* misc */
      .jive-widget { margin-bottom: 10px !important; }
      .j-column { margin-bottom: 10px !important; }
  
      /* ------------------
          Treatment for narrow window
          Method 1 (minimum optimisation)
  
          Adjust thread list table's shift and margin to maximize its width.
      */                                                                             
      /* ------------------ (currently active) */
      .j-layout-sl.j-browse-content .j-column-wrap-l { margin-left: -166px !important; }
      .j-layout-sl.j-browse-content .j-column-l      { margin-left: 166px !important; }
      .j-layout-sl.j-browse-content .j-column-s      { width: 166px !important; }
      /* ------------------ */
      /* ------------------
          Treatment for narrow window
          Method 2 (more beneficial to narrow window but has disadvantage for wide window)
         
          Let thread list table have full width but not exceed 1019px to make room for sidebar ui (filters & actions).
          If window is wide enough (>=1265px), sidebar ui is displayed next to thread list table,
          otherwise it is displayed below or above it (depending upon its document tree order).
         
          * sidebar width (constant)    = 166px
          * thread table max width      = 1019px
          * canvas margin-left          = 40px
          * canvas margin-right         = 40px
          ---------------------------------------
          * total                       = 1265px
      */                                                                             
      /* ------------------ (currently commented out) */
  /*
      .j-layout-sl.j-browse-content .j-column-wrap-l { max-width: 1019px !important; }
      .j-layout-sl.j-browse-content .j-column-wrap-l { margin-left: 0px !important; }
      .j-layout-sl.j-browse-content .j-column-l      { margin-left: 0px !important; }
      .j-layout-sl.j-browse-content .j-column-s      { width: 166px !important; }
  */
      /* ------------------ */
  
      /* ------------------
          Swap left-right positions of thread list table and sidebar ui (filters & actions)
      */                                                                             
      /* let thread list table float left */
      .j-layout-sl.j-browse-content .j-column-wrap-l,
      .j-layout-sl.j-browse-places .j-column-wrap-l { float: left !important; }
  
      /* let sidebar ui float right */
      .j-layout-sl.j-browse-content .j-column-s,
      .j-layout-sl.j-browse-places .j-column-s { float: right !important; }
      /* ------------------ */
  
      /* ------------------
          leader board
      */
      /* .jive-widget.jive-box.j-rc5.jive-widget-leaderboardwidget */
     
  /*
      .jive-widget-leaderboardwidget {display: none !important; }                    
  */
  
      .jive-widget-leaderboardwidget { max-width: 1000px !important; }                       
      .jive-widget-leaderboardwidget .j-bigtab-nav .j-tabbar { padding-top: 10px !important; }
      .jive-widget-leaderboardwidget .jive-widget-topmembers.split-columns ul li { min-height: 0px !important; }
      .jive-widget-leaderboardwidget .top-member-username,
      .jive-widget-leaderboardwidget .top-member-username * { font-size: inherit !important; }
      .jive-widget-leaderboardwidget .user-level-points {
          font-size: 18px !important;
          margin: 14px 0px !important;
          width: 60px !important;
          height: 30px !important;
          padding: 8px 0px 0px !important;
      }
      .jive-widget-leaderboardwidget .top-member-profile-info > a {
          border-radius: 0% !important;
          width: 60px !important;
          height: 60px !important;
      }
      .jive-widget-leaderboardwidget .pagination-class { margin-top: 30px !important; }
      /* ------------------ */
  
      /* article list
          .j-rc5 is used to identify this list
          e.g., https://discussions.apple.com/article/HT1939 */                      
      .j-layout-sl.j-browse-content.j-rc5 #jive-body-maincol { margin: 0px 0px 0px 166px !important; }
  
      /* ------------------------------------------------------------------------------------------------
          THREAD CONTENT BROWSER
      */
      /* thread header */
      .apple-thread-header {
          width: auto !important;
          margin-bottom: 10px !important;
          margin-left: 40px !important;
      }
  
      /* thread message */                                                                    /* NEW */
      .j-thread .jive-content .j-thread-post .jive-rendered-content {
          font-size:   inherit !important;
      }
      .j-thread #body-apple .jive-thread-messages h2.helpful-allreply,
      .j-thread #body-apple #helpful-container,
      .j-thread #body-apple .j-thread-post > header .j-post-author,
      .j-thread #body-apple .thread-container-wrapper,
      .j-thread #body-apple .all-replies-container,
      .j-thread #body-apple #j-main #jive-breadcrumb,
      .j-thread #body-apple .addReply,
      .j-thread #body-apple #jive-body-intro-content {
          max-width: inherit !important;
          margin: 10px 40px !important;
      }
      .j-inresponse-to {
          font-size: inherit !important;
      }
      .j-thread .jive-content .j-thread-post > header,
      .j-thread .jive-content .j-thread-post > h3.header {
          margin: 15px 0px 10px 0px !important;
      }
  
      /* thread original messeage (question) */                                               /* NEW */
      .j-thread-post section.j-original-message {
          margin: 0px 30px !important;
          padding: 15px 10px !important;
          border-style: dotted !important;
          border-width: thin !important;
          background: none repeat scroll 0% 0% rgb(247, 247, 237) !important;
      }
      .j-thread-post section.j-original-message h1 {
          max-width: inherit !important;;
          margin: 0px 60px 20px 60px !important;;
      }
      .j-thread-post section.j-original-message .jive-rendered-content {
          max-width: inherit !important;;
          margin: 0px 25px !important;;
      }
     
      /* original poster profile header */
      .j-thread .jive-content .j-thread-post > header.js-original-header {
          max-width: inherit !important;
          margin: 0px 40px !important;
          padding: 5px !important;
      }
  
      .j-thread-post section .thread-actions {
          max-width: inherit !important;
          margin: 0px 25px !important;
      }
      .j-original-message .jive-rendered-content p {
          font-size:   inherit !important;
      }
      .meta-posted {
          max-width: inherit !important;
          margin: 10px 25px 20px !important;
      }
      /* Q mark */
      .j-original-message h1 .q-marker {
          left: -60px !important;
          font-size: 32px !important;
      }
      
  
      /* answer rollup */                                                                     /* NEW */
      .j-answer-rollup.span-full-width {
          background: none repeat scroll 0% 0% rgb(237, 247, 232) !important;
          padding-bottom: 10px !important;
          margin: 20px 0px 0px 0px !important;
          border: 1px solid rgb(45, 184, 71) !important;
      }
      .j-inline-correct-answer {
          padding: 0px !important;
          max-width: inherit !important;
          margin: 0px 10px !important;
      }
      .j-inline-correct-answer section {
          margin: 10px 0px !important;
      }
      /* A mark */
      .j-inline-correct-answer .answer-marker {
          left: 0px !important;
          font-size: 32px !important;
      }
      
  
      /* persistent question shown at top */                                                  /* NEW */
      .persist-question.persist { display: none !important; }
  
     
      /* Solved and Helpful marker text */                                                    /* NEW */
      .j-thread-post header .j-correct-text,
      .j-thread-post h3.header .j-correct-text,
      .j-thread-post header .j-helpful-text,
      .j-thread-post h3.header .j-helpful-text {
          font-size: 22px !important;
          background: none repeat scroll 0% 0% transparent !important;
          border-style: none !important;
          margin: 0px !important;
          padding: 10px !important;
      }
  
     
      /* thread content */
      .j-thread .jive-content { margin: 0px 10px 0px 10px !important; }                       /* CHANGED */
  
     
      /* thread replies ul */
      ul.jive-discussion-replies.jive-discussion-indent-0 { margin: 0px !important; }
     
      /* thread reply li */
      .jive-discussion-replies li.reply { margin-top: 15px !important; }
  
      /* thread message border */                                                             /* NEW */
      .jive-discussion-replies li.reply .jive-thread-message {
          border-style: dotted !important;
          border-width: thin !important;
      }
  
      /* orgininal poster comment background */                                               /* NEW */
      .original-poster-comment {
          background: none repeat scroll 0% 0% rgb(247, 247, 237) !important;
          top:    0px !important;
          right:  0px !important;
          bottom: 0px !important;
          left:   0px !important;
      }
  
      /* pagenation */                                                                        /* NEW */
      .j-thread .jive-thread-messages .j-pagination {
          margin: 30px 0px !important;
      }
  
      /* promoted helpful answer and prompted recommended answer */                           /* NEW */
      .j-inline-promoted-helpful-answer,
      .j-inline-recommended-answer {
          background: none repeat scroll 0% 0% rgb(247, 232, 207) !important;
          padding: 15px 10px 5px 10px !important;
          margin: 0px 10px 15px 10px !important;
          border-style: dotted !important;
          border-width: thin !important;
      }
      .j-inline-promoted-helpful-answer p {
          margin: 0px !important;
      }
      .j-inline-promoted-helpful-answer header .reply-date,
      .j-inline-promoted-helpful-answer h3.header .reply-date,
      .j-inline-recommended-answer header .reply-date,
      .j-inline-recommended-answer h3.header .reply-date {
          font-size: inherit !important;
          margin: 10px 0px !important;
      }
      .j-inline-promoted-helpful-answer header .j-helpful-text,
      .j-inline-promoted-helpful-answer h3.header .j-helpful-text,
      .j-inline-recommended-answer header .j-helpful-text,
      .j-inline-recommended-answer h3.header .j-helpful-text {
          font-size: 22px !important;
          background: none repeat scroll 0% 0% transparent !important;
          border-style: none !important;
          margin: 0px !important;
      }
      .j-inline-promoted-helpful-answer section .reply-body,
      .j-inline-recommended-answer section .reply-body {
          font-size: inherit !important;
          margin-bottom: 20px !important;
      }
      .j-inline-promoted-helpful-answer section,
      .j-inline-recommended-answer section {
          padding: 0px 20px !important;
      }
      #helpful-container { padding-top: 0px !important; }
      #helpful-container hr { margin: 10px !important; }
      #helpful-container .more-answers { margin: 0px !important; }
      #helpful-container .more-answers * { font-size: 24px !important; }
  
      /* inline correct answer, helpful answer background */                                  /* NEW */
      div[itemprop="acceptedAnswer"] {
          background: none repeat scroll 0% 0% rgb(237, 247, 232) !important;
      }
      .j-thread .jive-content.j-helpful,
      .j-thread .jive-content.j-helpful.j-op {
          background: none repeat scroll 0% 0% rgb(247, 232, 207) !important;
      }
  
      /* switch between 'hellpful replies only' and 'all replies' */                          /* NEW */
      .jive-thread-messages .helpful-all-switch * {  
          font-size: 24px !important;
      }
      .jive-thread-messages .helpful-all-switch li.inactive {
          padding: 0px !important;
          top: 32px !important;
      }
      .jive-thread-messages .helpful-all-switch li.inactive span.menu {
          width: auto  !important;
          min-width: 160px !important;
          padding: 5px  !important;
          text-align: center !important;
      }
      
  
      /* thread content footer profile */                                                     /* NEW */
      .j-thread-post section.j-original-message footer .footer-profile {
          margin-right: 10px !important;
      }
      .j-thread-post footer .footer-profile {
          margin-right: -10px !important;
      }
      .j-thread-post footer .footer-profile .j-status-level {
          padding: 0px 10px 0px 0px !important;
      }
      .j-thread-post footer .footer-profile .username,
      .j-thread-post footer .footer-profile .jive-username-link {
          padding: 0px 10px 0px 10px !important;
      }
      .j-inline-correct-answer footer .footer-profile .j-status-levels,
      .j-inline-promoted-helpful-answer footer .footer-profile .j-status-levels,
      .j-inline-recommended-answer footer .footer-profile .j-status-levels {
          padding: 0px 10px 0px 0px !important;
      }
      .j-inline-correct-answer footer .footer-profile .username,
      .j-inline-promoted-helpful-answer footer .footer-profile .username,
      .j-inline-recommended-answer footer .footer-profile .username {
          padding: 0px 10px 0px 10px !important;
      }
  
      /* text wrap in header */
      .j-thread-post > header .j-post-author { white-space: normal !important; }     
     
      /* thread post section (message body) */
      .j-thread-post section {
          padding: 0px 20px !important;
          margin-bottom: 6px !important;
      }
      
  
      /* thread rendered content */
      .jive-rendered-content { padding-bottom: 4px !important; }
     
      /* thread rendered content quote & pre */
      .jive-rendered-content .jive-quote,
      .jive-rendered-content .jive-pre {
          margin: 5px 15px !important;
      }
  
      /* thread reply footer (Return to Community | Go to original post) */
      #jive-thread-reply-footer { margin-top: 10px !important; }
     
      /* more like this links, incomming links */
      #apple-related-threads { margin: 0px 40px !important; }
      #apple-related-threads .j-box { margin-bottom: 0px !important; }
      .j-icon-list li { padding: 3px 0px 3px 22px !important; }
  
      /* related articles */                                                         
      .apple-sidebar-property {
          width: auto !important;
          padding-left: 0px !important;
      }
      .jive-box-body.jive-sidebar-body.jive-sidebar-body-related-articles { padding: 15px 0px !important; }
      
  
      /* ------------------
          staus level, expertise, level points
      */
      /* status level expertise tile */
      .j-status-level.expertise-tile,
      .status-tile.expertise-tile { display: none !important; }                  
     
      /* status level level points */
      .j-status-level .level-points span { display: inherit !important; }            
      .j-status-level .level-points { white-space: inherit !important; }             
      /* ------------------ */
  
      /* ------------------------------------------------------------------------------------------------
          INLINE EDITOR
      */
      /* editor */
      .jive-discussion-replies li.addReply { margin: 50px 40px 0px !important; }
  
      /* ------------------------------------------------------------------------------------------------
          ADVANCED EDITOR
      */
  
      /* content area */
      .j-thread.jive-body-formpage #body-apple .j-form {
          max-width: inherit !important;
          margin: 0px auto 20px !important;
          width: inherit !important;
      }
      .j-thread .jive-content.jive-create-thread,
      .jive-body-formpage-document .jive-content.doc-page {
          margin: 0px 40px !important;
          padding: 0px !important;
      }
  
      /* editor panel */
      .j-thread .jive-content.jive-create-thread #jive-compose-title,
      .j-thread .jive-content.jive-create-thread .jive-editor-panel.jive-large-editor-panel,
      .jive-body-formpage-document .jive-content.doc-page #jive-compose-title,
      .jive-body-formpage-document .jive-content.doc-page .jive-editor-panel.jive-large-editor-panel { margin: 0px !important; }
  
      /* line height in editor */
      body.tiny_mce_content { line-height: inherit !important; }
  
      /* replying to */
      p.jive-replying-to { padding: 20px 0px !important; }
      .jive-body-formpage-comment .jive-thread-message { margin: 0px 40px 0px 80px !important; }
  
      /* reply to avatar */
      .j-thread-post header .j-post-avatar {
          position: absolute !important;
          top: 0px !important;
          left: -50px !important;
          width: auto !important;
      }
     
      /* buttons (Reply|Cancel) */
      .j-publishbar,
      .jive-body-formpage .jive-composebuttons { margin: 20px 40px 0px !important; }
  
      /* ------------------------------------------------------------------------------------------------
          ACTIVITY STREAM
      */
      /* activity entry */
      .j-act-entry { padding: 5px 0px 10px 100px !important; }
  
      /* activity title */
      .j-body-home .j-act-title { padding: 5px 0px 5px 24px !important; }
  
      /* activity body & comment */                                                  
      .j-body-home .j-act-init { padding: 5px 0px 10px 100px !important; }
      .apple-activity-comments-wrapper { margin-left: 0px !important; }
  
      /* Like list */
      .j-act-grouped .j-act-g-item { padding: 3px !important; }
     
     
      /* ------------------------------------------------------------------------------------------------
          SEARCH RESULTS
      */
      /* search result entry */
      .j-search-results-main-container .j-search-result { padding: 10px !important; } 
  
      /* ------------------------------------------------------------------------------------------------
          DOC (USER TIP)
      */                                                                             
      /* user tip canvas */
      .jive-body-content.j-doc .j-column-wrap-l { margin: 0px 40px !important; }
  
      .j-doc .jive-content {                                                                  /* NEW */
          margin: 0px !important;
          padding: 10px !important;
          border: thin dotted !important;
      }
  
      /* ------------------------------------------------------------------------------------------------
          PROFILE
      */                                                                             
      /* header & navigation bar (Bio|Activity|Content|Communities) */
      .j-view-profile .j-page-header { padding: 10px 40px !important; }
      .j-bigtab-nav { margin: 10px 40px !important; }
     
      /* Bio */
      .j-layout-l .j-column-wrap-l { width: 100% !important; }
  
      /* Communities (places) sidebar ui blue marker adjustment
          (according to the sidebar width changed to 166px from 180px for selector: .j-layout-sl.j-browse-places .j-column-s
          in PLACES section)  */
      .j-view-profile .j-second-nav ul > li.active  { width: 156px !important; }
  
      /* ------------------
          profile specialties and awards
      */
      /* profile status container for specialties and awards */
      .jive-view-profile .profile-status-container { display: none !important; }              /* REFINED */                   
  
      /* profile modal note status row for specialties and awards */
      .status-row { display: none !important; }                                      
      /* ------------------ */
  
      /* ------------------------------------------------------------------------------------------------
          PLACES
      */                                                                             
      /* latest activity column */
      .j-browse-details .j-td-activity { max-width: 650px !important; }
  
      /* ------------------
          Treatment for narrow window
          Method 1 (minimum optimisation)
  
          Adjust community list table's shift and margin to maximize its width.
      */                                                                             
      /* ------------------ (currently active) */
      .j-layout-sl.j-browse-places .j-column-wrap-l { margin-left: -166px !important; }
      .j-layout-sl.j-browse-places .j-column-l      { margin-left: 166px !important; }
      .j-layout-sl.j-browse-places .j-column-l      { padding-left: 0px !important; }
      .j-layout-sl.j-browse-places .j-column-s      { width: 166px !important; }
      /* ------------------ */
      /* ------------------
          Treatment for narrow window
          Method 2 (more beneficial to narrow window but has disadvantage for wide window)
         
          Let community list table have full width but not exceed 1019px to make room for sidebar ui (filters & actions).
          If window is wide enough (>=1265px), sidebar ui is displayed next to community list table,
          otherwise it is displayed below or above it (depending upon its document tree order).
         
          * sidebar width (constant)    = 166px
          * community table max width   = 1019px
          * canvas margin-left          = 40px
          * canvas margin-right         = 40px
          ---------------------------------------
          * total                       = 1265px
      */                                                                             
      /* ------------------ (currently commented out) */
  /*
      .j-layout-sl.j-browse-places .j-column-wrap-l { max-width: 1019px !important; }
      .j-layout-sl.j-browse-places .j-column-wrap-l { margin-left: 0px !important; }
      .j-layout-sl.j-browse-places .j-column-l      { margin-left: 0px !important; }
      .j-layout-sl.j-browse-places .j-column-l      { padding-left: 0px !important; }
      .j-layout-sl.j-browse-places .j-column-s      { width: 166px !important; }
  */
      /* ------------------ */
  }
  

  Good luck

  H

• Widget deployment problem

  I'm new to the blackberry widget dev process so bear with me. I have trouble getting my widget to work on the device itself. Here's what I did to get to where I am so far:

  1 developed a web application (Calculator). Coded in html, Javascript and css by hand.

  2. I made the recalcitrant xml file and images folder etc so it runs on a Blackberry device

  3. it works perfectly in the Simulator on my machine

  4. I bought, received and installed the signing keys. I think this has been done correctly because I followed the documentation and he went to the way it was supposed to, so know a reason to think that the keys are bad.

  5. update of the widget with the widget of REM conditioner.

  6 use BlackBerry desktop software to install the files on the device .alx file

  Now, I have it on the device and I always get the error "trying to access a secure api."

  What I am doing wrong? Any help would be awsome.

  D.

  When packing your widget, you must use the indicator/g so that she could sign the COD file, as part of the build process.

  You can sign your application later too.  To do this, run the SignatureTool.jar file located in the BlackBerry Widget SDK installation directory bin, select your COD file and click on the button request Signatures.

• Working with PHP in Widgets

  Hi, I have just a few questions about PHP with Widgets:

  1. I've read in a few places that you can use PHP in Widgets, but when I tried to include an index.php in my Widget, it notified me that he has not been supported. So I guess I must have my PHP stored on a remote server and bind it using an anchor for example. (Also white list my field).

  If it works, I'm still able to access those Widget API? I have a Javascript with a few Blackberry Menu API file and would like to know if these still work when they are on my remote server.

  2. If I have a remote PHP file and a remote JS file does not work, how I would approach to access a local copy of the JS file that I compiled with the widget?

  I ask these questions because I have a lot of dynamic pages, I'd like to see on my Widget, but would also have the API Widget at hand, as well for menus and other.

  Thank you!

  1. I've read in a few places that you can use PHP in Widgets, but when I tried to include an index.php in my Widget, it notified me that he has not been supported. So I guess I must have my PHP stored on a remote server and bind it using an anchor for example. (Also white list my field).

  Correct... you can not add a PHP page directly in the Archives of your widget.  You can either make it in your widget by white first listing of the URLS in the file config.xml elements and then going to your page via an anchor tag or the definition of the location.href via JavaScript.

  You can also call your PHP via AJAX scripts if you use them to turn the pieces of HTML or data.

  If it works, I'm still able to access those Widget API? I have a Javascript with a few Blackberry Menu API file and would like to know if these still work when they are on my remote server

  Yes, you are still able to access your Widget API from your pages side server.  Each API you wish to access must have its id function declared for the field in the white list.  For example, if your page is located at 'http://www.foo.com' and you want to have access to the API of blackberry.ui.menu... your config.xml element will look like the following:

  http://www.foo.com" subdomains="true">
    
  
  

  This will allow any page that is loaded from the www.foo.com field to access the API JavaScript menu.  This allows you to place the functional parts of your widget where they make sense for your application.

  There is another parameter config.xml that you will be probably interested as well.  You can define your own custom for a BlackBerry Widget header value.  It is thus on your side server PHP code, you can check to make sure that your real widget hitting your PHP script.  The attribute is called "rim: header ' and is located in the root element.  You can consult the Guide to the developer for further details if you are interested.

  2. If I have a remote PHP file and a remote JS file does not work, how I would approach to access a local copy of the JS file that I compiled with the widget?

  Number 1) will work, but you can also do what you ask for (2).  Your PHP page of code on server side, you have white listed and displayed in the widget, has access to your local resources of the widget.  It is quite convenient for common resources that you do not want to draw on the network such as images, css, and JavaScript.

  You can link to these resources by setting their path in your HTML to 'local:///myimage.png '.  The "local: / / /" is a local path that begins at the root of archive widget.  For example if you want to load an image from the local widget it would look like the following:

  I hope this helps

• WebWorks and widget is the same?

  WebWorks and widget is the same?

  The BlackBerry Application Platform WebWorks is an evolution of what exists only in the development of Widget SDK.  They are not the same.

  The BlackBerry Application Platform WebWorks is just that - a platform - to create BlackBerry applications.

  More than a developer tool, it is the platform that encompasses all the development tools available, supported technologies and services that are available for developers to use to create applications fully functional BlackBerry using web technologies such as HTML, CSS and JavaScript.

  The BlackBerry Application Platform WebWorks is:

  • Rendering engine for the blackBerry browser powered by WebKit - supports HTML5 and CSS3
  • Project open Source -community participation is welcomed and encouraged.
  • Development tools - BlackBerry Web plug-ins for Eclipse. BlackBerry Web plugin for Microsoft Visual Studio and the BlackBerry Widget Packager
  • Services of the future platform such as advertising, payment, analytics and BBM.

• CSS refresh after javascript DOM change (tab Ajax control) and also refresh the list of objects of Navigation

  Hi all

  When I access a Web page, that I created in the browser or Widget that uses an ASP.NET Ajax Control Toolkit Tabs the action of switching between tabs works well but the tab header does not reflect the change to display the active tab.

  In a standard browser of the tab header will be change / light tone based on the css classnames active Ajax control for settings changes dynamically in the DOM when switching between tabs and I was wondering if maybe the BB browser will not reflect/refresh css when changes on the client side affect the DOM? If that's the case (?) is there a way to force that change somehow?

  Also in the same direction and on the similar question I posted yesterday on switching between Navigation power user mode in a Widget, so javascript client-side dynamically is change the 'x-blackberry-focus' of a DOM object possible to have the change reflected in the Navigation objects? Or is the list of objects that can be traversed only generated load initial page and cannot change without a new post?

  Thank you

  Derek

  I solved the problem with the Ajax Control Toolkit TabContainer uisng having to do a "dummy" DOM change in the TabHeader after that the tab is passed between the tabs then forcing the refresh and repaint the tab headers.

• Html and css site design

  Hello

  Does anyone have a nice easy way to create widget BB pages in a normal browser before moving a Widget? I'm going nuts making a tweak, debugging of pressing, in expectation of the build to succeed, checking my widget, tweaking some css more etc etc.

  I'm sure I saw an article somewhere on how to do it outside of the Simulator, but I'll be damned if I can find it again

  any help much appreciated

  see you soon

  Lee

  The easiest way that I do is the following:

  (1) put my source of the widget on a shared folder on a web server

  (2) set my config.xml file to have its starting point to the page on my web page server

  (3) whitelist the domain where my source of the widget is on my web server

  (4) adds a Menu item "Refresh" in a common *.js file do a refresh of the standard browser

  (5) to build and run the widget in the Simulator

  So I can make all the settings in HTML and CSS I love and you simply press the element menu to update in the Simulator.

  The only time wherever I need to re - build, it's if I modify a config.xml file.  Then when I'm satisfied, I simply change my config.xml file to package resources locally and make a final test.

• How to operate the application widget.

  Hello refugees,

  I am new to the BB mobile development. I created a gadget application containing (css, js, config.xml, html files). I have all the zipped in a single folder and copied in Motion\BlackBerry Widget Packager\web research program .

  When I use comand prompt to run it: what's happening: -.

  [INFO]          The analysis of the parameters of the option
  [INFO]          Bbwp.properties analysis
  [INFO]          Validation of zip archive
  [ERROR] config.xml not found

  One can suggest/help me...

  Thank you

  Pankaj Perron

  Did you add the class path to your PATH variable as shown here:

  

• Help with my Buddy purchase real estate Widget

  Hello

  I work with a client who needs widget with my buddy on his website purchase. I have everything set up and works but there is a glitch with text getting crushed, at MBB people say it's because I use «!» important' in my script; Please see this excerpt from training resources page, museutils.js:

  };

  Muse.Utils.getNaturalWidth = {function (b)}

  var a = - 1;

  b.naturalWidth! =

  null? a = b.naturalWidth: b.runtimeStyle? (b.runtimeStyle.width = 'auto', b.runtimeStyle.height = 'auto', b.runtimeStyle.borderWidth is '0', '0' = b.runtimeStyle.padding, a = b.offsetWidth, b.runtimeStyle.width is "", b.runtimeStyle.height = "", b.runtimeStyle.borderWidth = "", b.runtimeStyle.padding = ""): (b = b.cloneNode(!0) = b.className "", b.style.width = "auto !) important', b.style.height = ' auto! important', b.style.borderWidth = ' 0 ! ' importantt ', b.style.padding = ' 0 ! important«(, un = b.width);»

  return a

  };

  Muse.Utils.getNaturalHeight = {function (b)}

  var a =

  -1;

  b.naturalHeight! = null? a = b.naturalHeight: b.runtimeStyle? (b.runtimeStyle.width = 'auto', b.runtimeStyle.height = 'auto', b.runtimeStyle.borderWidth is '0', '0' = b.runtimeStyle.padding, a = b.offsetHeight, b.runtimeStyle.width is "", b.runtimeStyle.height = "", b.runtimeStyle.borderWidth = "", b.runtimeStyle.padding = ""): (b = b.cloneNode(!0) = b.className "", b.style.width = "auto !) important', b.style.height = ' auto! important', b.style.borderWidth = ' 0 ! important', b.style.padding = ' 0 ! important«(, un = b.height);»

  return a

  };

  I have no idea how to do to remove this ! important for the widget to work correctly. Is there anyone who might be able to help me.

  Thank you

  The code is generated by Muse when you publish the site. The only way to remove it would be to change the code once it is downloaded.  You must also change whenever you publish, as it would be crushed. I certainly wouldn't recommend, though, as probably break you the rest of your design.

  The easiest fix for fix would be to use the! important tag in the CSS in the plugin you are using, if possible. His goal is to force a substitution to all styles defined elsewhere.

  I hope this helps.

  David

  Creative muse

• Problem with html/css object in Muse

  I did a project Muse and use widgets, but when I try to measure with the html/css object provided by Muse, the preview works perfectly but when I put it on Business Catalyst, the changes disappeared and he is back to normal...
  What should I do to make the CSS works?

  I don't know how you managed to add css to Jotform. JotForm is broadcast via iframe. Not editable any it by the css on your side. Any change in appearance, you can do in the Online Form Builder · JotForm , non-personalized css.

  

  Well, if we talk in general. Muse never deletes the user code inserted into the head through the properties of the page. But I do not see any css custom in the source code of your website.

• Twitter feed widget disappears when a breakpoint

  Hi all

  My question is the same as this thread, but is not resolved by starting on a new/white site:

  Twitter feed widget disappears on sensitive site

  I copied the html code of twitter and glued directly to my page, everything shows up with my diet and works fine on my window design, but when I upload it to my site or I saw in the browser, it the widget will disappear when it reaches a breakpoint and will not return if the browser is again tense. If done throughout the site flashes through breakpoints. (the built-in Facebook widget does not work)

  I updated and reinstalled muse and tried on two computers, the other a mac with the same results, I tried also everything suggested in the link above.

  Please help, thanks in advance

  Sam

  Hi Sam,

  Œuvres of Muse on breakpoints to generate a responsive structure of the Web site.

  If you add any external HTML code in Muse, then when you go from a breakpoint to another that the css property changes when you preview on 960px his watch the feed (Twitter), but when you reduce the width of the browser to reach 620px it reloads the css property to 620px who is not related to the inserted HTML.

  Workaround: add the code to the 960px and brand it as "Hide in other breakpoints" now, go to 620px breakpoint in Muse and add code here select "hide in other breakpoints.

  This means that you must add the code separated into separate breakpoints.

  Hope that works!

  Thank you

  Prabhakar Kumar

• Problem with script in widget Muse

  Hello, all pages will appear at the top #u5501.size_fluid_width_height iframe {position: absolute; left: 0; top: 0 ;}} ???

  See line 59 and 60 of the source code

  <!--code HTML Widget - >
  	< style type =""text/css ">#u5501.size_fluid_width_height iframe {position: absolute; left: 0; top: 0 ;}}" < / style >

  on the staff of the site: http://www.Sejour-au-Vietnam.com

  site on Catalys: trip and stay in AsieAmo TravelAcueil

  Best regards, Serge Jullian

  jullians63645149 wrote:

  personal site: http://www.Sejour-au-Vietnam.com

  I get nothing at this address

  jullians63645149 wrote:

  the site of Catalys: trip and stay in AsieAmo TravelAcueil

  you did the wrong code...

  

  ... what you trying to do with the iframe?