Time keeps on breaking, breaking, breaking...
-
The "fucking useless time ago" text keeps randomly vanishing. I'll do a hard refresh, it comes back, and then for no reason go away again. I just did a hard refresh, and the next click it was gone.
http://i.imgur.com/dc6yBrg.png
(the actual date time is just css :before and :after so I can see actual dates and times).
This has happened on FF22 and Chrome.
-
It's not consistent for me.
I buttume age is related?
-
@Arantor I think, if it's older than [insert actual duration here], it just shows the date rather than a 'humanised' phrase
-
@RaceProUK said in Time keeps on breaking, breaking, breaking...:
@Arantor I think, if it's older than [insert actual duration here], it just shows the date rather than a 'humanised' phrase
"Actual duration" seems to be "two months," +/- discorounding. At least that was the biggest "ago" I saw scrolling through the topic list; topics 3-ish months or older showed the specific date.
-
@Lorne-Kates I see $(".timeago").timeago(); on app.processPage handler, and wonder if adding that line to $(document).ready() handler will be enough to fix it.
-
@cheong said in Time keeps on breaking, breaking, breaking...:
@Lorne-Kates I see $(".timeago").timeago(); on app.processPage handler, and wonder if adding that line to $(document).ready() handler will be enough to fix it.
Maybe? Maybe someone who develops this site should think about that, so their shit isn't broken?
-
@Lorne-Kates said in Time keeps on breaking, breaking, breaking...:
@cheong said in Time keeps on breaking, breaking, breaking...:
@Lorne-Kates I see $(".timeago").timeago(); on app.processPage handler, and wonder if adding that line to $(document).ready() handler will be enough to fix it.
Maybe? Maybe someone who develops this site should think about that, so their shit isn't broken?
Pfft, you're clearly getting old, the new generation of web developers don't work this way.
-
@Arantor said in Time keeps on breaking, breaking, breaking...:
@Lorne-Kates said in Time keeps on breaking, breaking, breaking...:
@cheong said in Time keeps on breaking, breaking, breaking...:
@Lorne-Kates I see $(".timeago").timeago(); on app.processPage handler, and wonder if adding that line to $(document).ready() handler will be enough to fix it.
Maybe? Maybe someone who develops this site should think about that, so their shit isn't broken?
Pfft, you're clearly getting old, the new generation of web developers don't work this way.
Seems it's fixed now, by the way.
-
@cheong yeah, Ben mentioned it in the changelog for the last forum update.
-
While we're talking about things to change, may I also suggest changing document.querySelectorAll(".post-tools").forEach( in nodebb.min.js to $(".post-tools").each( just to support older browsers?
It don't work on IE11, not sure about other browsers.
-
@cheong Pfft, no-one uses IE11, Edge is where it's at. NO-ONE USES ANYTHING LESS THAN BLEEDING EDGE BROWSERS NOW. (Pun not intended.)
AND IF YOU DO IT'S YOUR OWN FAULT THE WEB IS A STEAMING PILE OF
I HAVE THESE VOICES IN MY HEAD MAKE IT STOP MAKE IT STOP M̥̩̭̮͢A̠̭̩͖K͙Ḙ̫̰̘̖̹̫ ̺̣̞̦̮I̛T͓̟̥͍ ̭̬̳̦̭S̘͔͍̹ͅTO̥̝̻̤̺P̟̟̭̹̙̬̥ M̢̬̯͖̘͙̤̿Å̙͔͚̮͔̗̗͒̒̈ͯ̃̚Ḳ̠͚ͥE̱͐̌ ̛̺̺ͫͮ͋͑I̷͖̫͚̘̼͛̑T̖̥̿̑̿ͪ͆̒ ̮̺͔͌ͬ͠Ș̈ͫ̓̏̄T̙͉̣̞̳̪ͣ́͞Ô̹͙̭̘̖̽͊ͦ̑͆̀Pͨ́ M̟͎͔̱͔ͭ͛ͮ̏ͅǍ̬̤̃̈ͣ̎̈͡ͅK̙͚̫̬̍͐̐̌͊͊͟͞͠Ȇ̞ͬ͟ ̡̡̭̓̽I͉̰ͮ̓T̴̢̯̳̟̠̙̲͍̮ͧͧͫͯͬͮ̋̐ ̻̪̤͇̮͖̳ͮ̍́S̲̣͙̀ͪͩͧŤ̛̪̮̭͙͐͑ͤ̓͞Ȍ̹̊̉̒̇͒ͦͅP̢͖̫̱̟̲͓̠ͭ̅̑̍ͅ Ṃ̺̘̪͕̥̰̍̄ͯ̈́̒͘A̹͈̞̺̻̹̙̩͓̝̣̻͋̽̒̈́̉ͪͥ̉̐̓̒͑̇ͩ͟ͅK̴̢̻̤͎̮̜͇̤͎̙͍͕̻̻͇̩̖ͥͫ̽̍̒ͬ̓̄̂͢͡E̶̴ͨ̅̒͛ͮ͛͏̱͍͉͚ ́ͬ̅ͪͤ̀҉̦̞̮̟̱̠I̸̩̜͓̹͔͖̫͛̋̈̐ͮͫͦͫ̑ͥ͑͜Ţ̗̖̠͎̩̘̪̿͒ͥ̎ͫͦ̀͜ ̵̢̨̛̬̰̤̲̳̺͎̬͚̗͍͕͉͙̗̥̎͗̓ͤ͑̐͗̍͊͛̅͒ͦ͊̏Ś̷̴͈̰̭̰̘̥͉̦͎͐ͣ͋̒̄́̏͆̌ͣ̑̉͋̌̓͊͊͘̕͠T̵̷̡̬̬̳̥̥̭̣̮̹̠͓̙͓ͨ͊͑̾̒ͤͦͦ͢͝Ó̴̧̡̱̯̜̬͉͇̦͚̟̣͓̦̝̦̜̃̎ͩ̾ͬͩͥ̚ͅP̴̧͎̱̤͈͆̅͑́̀̚͡͠
I despise modern web developers. I walk amongst them but I am not one of them.
I am a pilgrim in an unholy land as I try to preach the faith of security, stability, and pages that don't need JavaScript to zebra-stripe tables or replace core browser functionality like form submission.
-
@Arantor Btw, based on MDN information, this won't work on Safari either.
Also seems for Firefox this feature is available only 10 days ago (v50 is released on 2016/11/15), very hot and new.
-
@cheong including Mobile Safari or Android, apparently.
-
@cheong said in Time keeps on breaking, breaking, breaking...:
While we're talking about things to change, may I also suggest changing document.querySelectorAll(".post-tools").forEach( in nodebb.min.js to $(".post-tools").each( just to support older browsers?
It don't work on IE11, not sure about other browsers.
FWIW, that's a user contributed script, not a NodeBB thing.
But cc @ben_lubar he's got a point
-
I have a different problem with times...
It's like that when I load the forum for the first time after opening Firefox
2250 and eventually fixes itself if I wait a bit and load /unread again, so it's weird.
-
@coderpatsy Just had that happen to me. Odd thing is, the times are correct when the page loads, then they go wrong.
It only happens in fresh tabs, at least as far as I can tell.
-
@RaceProUK Ah yes, the browser opening bit was a red herring, it's just a whole page (re)load thing.
-
Timestamps wrong on cold load · Issue #5237 · NodeBB/NodeBB
Please include the following information when submitting a bug report/issue: NodeBB version and git hash (to find your git hash, execute git rev-parse HEAD from the main NodeBB directory) https://g...
-
-
@ben_lubar
Lesson of the Day: always pre-heat the oven before loading it
-
@ben_lubar 'forum software built for the modern web', does that mean it's built for and to be used by people with CADT where they can't decide which date format is the one true format? (And why we hate it so much?)
-
@Arantor said in Time keeps on breaking, breaking, breaking...:
(And why we hate it so much?)
Dr. Datelove, or how I stopped worrying and started loving UTC Time.
-
@Luhmann said in Time keeps on breaking, breaking, breaking...:
@Arantor said in Time keeps on breaking, breaking, breaking...:
(And why we hate it so much?)
Dr. Datelove, or how I stopped worrying and started loving
UTC TimeISO 8601 Format.FTFY
-
@Arantor said in Time keeps on breaking, breaking, breaking...:
@Luhmann said in Time keeps on breaking, breaking, breaking...:
@Arantor said in Time keeps on breaking, breaking, breaking...:
(And why we hate it so much?)
Dr. Datelove, or how I stopped worrying and started loving
UTC TimeISO 8601 Format.FTFY
Specifically, RFC 3339 timestamps that end with "Z".
-
@ben_lubar still cromulent with ISO 8601 ;)
-
Btw, I get fed up with that many variance of DateTime format that customer request us to accept on the web page, so I just feed it into moment and see if it's a valid time, if not .isValid() then reject it.
-
@Arantor said in Time keeps on breaking, breaking, breaking...:
I despise modern web developers. I walk amongst them but I am not one of them.
I'd suggest carrying a machete.
-
@cheong said in Time keeps on breaking, breaking, breaking...:
While we're talking about things to change, may I also suggest changing document.querySelectorAll(".post-tools").forEach( in nodebb.min.js to $(".post-tools").each( just to support older browsers?
It don't work on IE11, not sure about other browsers.
Those willy web-sub-standards.
You can alternatively just smack a polyfill on it, though, no?
-
@coderpatsy said in Time keeps on breaking, breaking, breaking...:
Ah yes, the browser opening bit was a red herring
NodeBB exhibits far fewer bugs when you don't open your browser.
