Results 1 to 5 of 5

Thread: Featured Content Glider - help with non-javascript presentation

  1. #1
    Join Date
    Dec 2007
    Posts
    16
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Default Featured Content Glider - help with non-javascript presentation

    1) Script Title: Featured Content Glider

    2) Script URL (on DD): http://www.dynamicdrive.com/dynamici...tentglider.htm

    3) Describe problem:

    Hi folks. I love the script and it works fine. I now need to make sure that the content is still accessible when javascript is not enabled.

    I have used <noscript>...</noscript> tags to enable the various separate segments of content to display vertically - so far so good. However, I would really like to have hidden the pagination / number / next / prev links at the bottom so that users without javascript enabled browsers will not get confused and find that these links don't actually do anything.

    Does anyone have any suggestions?

    Many thanks
    Last edited by Jeremy; 01-08-2010 at 02:26 PM. Reason: fix typo

  2. #2
    Join Date
    Mar 2005
    Location
    SE PA USA
    Posts
    30,495
    Thanks
    82
    Thanked 3,449 Times in 3,410 Posts
    Blog Entries
    12

    Default

    Put this in your stylesheet:

    Code:
    .toc, .prev, .next {
            display: none;
    }
    Then at the beginning of the featuredcontentglider.js file add the highlighted:

    Code:
    //Featured Content Glider: By http://www.dynamicdrive.com
    //Created: Dec 22nd, 07'
    //Updated (Jan 29th, 08): Added four possible slide directions: "updown", "downup", "leftright", or "rightleft"
    //Updated (Feb 1st, 08): Changed glide behavior to reverse direction when previous button is clicked
    //Updated (Feb 12th, 08): Added ability to retrieve gliding contents from an external file using Ajax ("remotecontent" variable added to configuration)
    //Updated (July 21st, 09): Updated to work in jQuery 1.3.x
    //Updated (Dec 13th, 09): Added keyboard navigation, so left/ right arrow keys now move glider. Fixed bug with auto rotation when "next" link isn't defined.
    
    document.write('<style type="text/css">.toc, .prev, .next {display: inline;}<\/style>');
    
    jQuery.noConflict()
    
    var featuredcontentglider={
    	leftrightkeys: [37, 39], //keycode
    - John
    ________________________

    Show Additional Thanks: International Rescue Committee - Donate or: The Ocean Conservancy - Donate or: PayPal - Donate

  3. #3
    Join Date
    Dec 2007
    Posts
    16
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Default

    Hi John,

    Many thanks - did as you asked but the pagination links still show when javascript is disabled.

    Any ideas?

  4. #4
    Join Date
    Dec 2007
    Posts
    16
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Default

    Hey John,

    I attempted using the class .glidecontenttoggler instead of .toc, .prev, .next in the external js file in the location you told me to and put 'display:none;' for the .glidecontenttoggler class in the CSS file and it now works. The pagination links are absent when javascript is disabled.

    I am assuming this solution is legitimate?

    Many thanks for helping me with this.
    Last edited by Jeremy; 01-08-2010 at 02:35 PM.

  5. #5
    Join Date
    Mar 2005
    Location
    SE PA USA
    Posts
    30,495
    Thanks
    82
    Thanked 3,449 Times in 3,410 Posts
    Blog Entries
    12

    Default

    That would be more straightforward, yes. But it should have worked the other way. I'd have to see all of the styles involved to know for sure exactly why it did not. If it came before this rule:

    Code:
    .glidecontenttoggler a{ /*style for every navigational link within toggler */
    display: -moz-inline-box;
    display: inline-block;
    border: 1px solid black;
    color: #2e6ab1;
    padding: 1px 3px;
    margin-right: 3px;
    font-weight: bold;
    text-decoration: none;
    }
    There's a good chance that would have overridden it.

    But, as long as it works now I'm not going to complain.

    However, if you were to have some <noscript> content in the glidecontenttoggler division(s), we could troubleshoot my first idea so that the <noscript> content in there could still show up without the controls.
    - John
    ________________________

    Show Additional Thanks: International Rescue Committee - Donate or: The Ocean Conservancy - Donate or: PayPal - Donate

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •