• Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
v3.5.2 Latest
Buy Hosting

A little problem with the new URL hashes

Scheduled Pinned Locked Moved Bug Reports
10 Posts 6 Posters 2.6k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • trevorT Offline
    trevorT Offline
    trevor Plugin & Theme Dev Anime Lovers GNU/Linux
    wrote on last edited by trevor
    #1

    I noticed the new changes made for the topic.tpl and the URL hashes.

    When scrolling through each post in any particular topic the URL #NUM at the end changes - which is cool, love it.

    Now when scrolling through on Chrome, not sure about any other browser, but on chrome the favicon flickers when scrolling either up or down. Additionally, while this nice to have, its also a tad bit CPU intensive on the client-side of things. Feels sluggish and unstable IMO.

    Does anyone else have the same problem?

    F 1 Reply Last reply
    0
  • K Offline
    K Offline
    kelso
    wrote on last edited by
    #2

    Im seeing the same behavior..

    1 Reply Last reply
    0
  • frissdiegurkeF Offline
    frissdiegurkeF Offline
    frissdiegurke Plugin & Theme Dev
    wrote on last edited by
    #3

    I don't see the favicon flickering (chrome too) but the 'reload' button always switches to 'stop' button (regardless if the title has changed on each scroll)
    So maybe it's just a missing check whether the location needs to change?

    trevorT 1 Reply Last reply
    0
  • trevorT Offline
    trevorT Offline
    trevor Plugin & Theme Dev Anime Lovers GNU/Linux
    replied to frissdiegurke on last edited by
    #4

    @frissdiegurke said:

    I don't see the favicon flickering (chrome too) but the 'reload' button always switches to 'stop' button (regardless if the title has changed on each scroll)
    So maybe it's just a missing check whether the location needs to change?

    The favicon and the reload flickers. @_@

    1 Reply Last reply
    0
  • F Offline
    F Offline
    finid
    replied to trevor on last edited by
    #5

    @trevor

    On a Linux box: The Reload/Stop button flickers on Chromium, but not on Firefox.

    1 Reply Last reply
    0
  • trevorT Offline
    trevorT Offline
    trevor Plugin & Theme Dev Anime Lovers GNU/Linux
    wrote on last edited by
    #6

    I'll test it on Firefox and Safari.

    1 Reply Last reply
    0
  • trevorT Offline
    trevorT Offline
    trevor Plugin & Theme Dev Anime Lovers GNU/Linux
    wrote on last edited by
    #7

    Seems to be working fine in FF.

    1 Reply Last reply
    0
  • barisB Offline
    barisB Offline
    <baris> NodeBB
    wrote on last edited by baris
    #8

    history.replaceState doesn't seem to play well with all browsers/platforms. I see the favicon reload button flicker occasionally. http://keyes.ie/pushstate-and-replacestate-bug-in-chrome/ and progress on the bug on chrome https://code.google.com/p/chromium/issues/detail?id=50298

    1 Reply Last reply
    0
  • julianJ Online
    julianJ Online
    julian GNU/Linux
    wrote on last edited by
    #9

    We wanted to go a simpler route with this... I originally thought we could just alter window.location.hash, but as it turns out, if you do that, on Firefox, it goes to the hash, whereas on Chrome, it does nothing. So that ruled out simplicity...

    1 Reply Last reply
    0
  • trevorT Offline
    trevorT Offline
    trevor Plugin & Theme Dev Anime Lovers GNU/Linux
    wrote on last edited by trevor
    #10

    Ah okay, thats more reasonable as it stands.
    Thanks @baris @julian for the clarification!

    1 Reply Last reply
    0

Copyright © 2023 NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development