You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
within lengthy conversations, individual statuses might disappear beneath the fold - e.g. if .../updates/3148 has numerous preceding messages within the same thread, only the thread's top messages are visible on page load
given the resource design and content layout constraints, I can't think of a decent solution though (I'd rather avoid a JavaScript hack)
The text was updated successfully, but these errors were encountered:
good point, I forgot to articulate my assumption there: I reckon it'd be weird if a status's canonical URI included a redundant anchor (.../updates/3148#3148)
well, I actually thought of something like <meta http-equiv="refresh" content="1;URL=#current"/> and adding the id="current" instead of class="current"
within lengthy conversations, individual statuses might disappear beneath the fold - e.g. if .../updates/3148 has numerous preceding messages within the same thread, only the thread's top messages are visible on page load
given the resource design and content layout constraints, I can't think of a decent solution though (I'd rather avoid a JavaScript hack)
The text was updated successfully, but these errors were encountered: