CSS change triggers resource error?
-
How is marking your posts green for a few minutes worse than giving you a whoosh badge or any other thing we do?
I can ignore all that shit. I can't ignore 47 page dimming error dialogs showing up while I'm trying to type a post.
-
I can't ignore 47 page dimming error dialogs showing up while I'm trying to type a post.
Hmm...I guess it's because it was your user? I definitely didn't get those. Sounds like it needs more testing (not with you, of course).
-
I got page-dimming errors as well.
-
Thirded -- the post coloring gave Discurse a Discowedgie somehow.
-
@tarunik Is Doing It Wrong™
-
I wager PJH knew exactly what he was doing with the errors. We talked about it just like yesterday or the day before. And he's the type to read every word in the bugs category.
-
I definitely didn't get those.
It was only a CSS change and as such, it certainly couldn't be directed to any particular user. Browser in use may possibly be relevant; e.g. I get quite a few errors on Mobile Chrome, but rarely see any on Firefox/Linux.
-
It probably triggered some impossibly-complex Rube Goldberg machine of Discourse bugs and WTFiness.
-
I wager PJH knew exactly what he was doing with the errors.
I can't imagine how you came to that conclusion.
We talked about it just like yesterday or the day before. And he's the type to read every word in the bugs category.
I don't remember that. Or haven't gotten to it yet....lemme look...
I see some talk about that in the Likes thread. But nothing that matches what you are remembering. Got a link or anything?
And the Likes stuff spun off this:
http://what.thedailywtf.com/t/you-are-not-permitted-to-view-the-requested-source/37057?u=boomzilla
But @PJH never posted there and I can't imagine what would connect that to this.
-
I get quite a few errors on Mobile Chrome, but rarely see any on Firefox/Linux.
That's certainly possible. I didn't get the errors on Chrome/Linux. I think @Yamikuronue, who said she got a bunch, uses Chrome/Windows.
-
uses Chrome/Windows.
My name is IJIJ, and I use Chrome on Windows to read WTDWTF....
I had a ton of "can't access resource" errors, before reopening the tab.
FWIW.
-
Chrome for Windows 7 as well.
In fact, I happened to get a screenshot:
Not that it helps, mind. I capped it because the fade-out was pure black, not just dim; I suspect there were multiple errors stacked on top of each other, because doesn't it usually just dim?
-
I randomly get those on occasion, usually during mundane tasks like opening a topic or liking a post.
-
I'm sure this filed someplace already but...
It's a PITA when your post gets moved want to follow the notification to your post...
"It got moved" TO WHERE?
Also, Windows 7 with Chrome. Seconding Yamikuronue's observation.
-
I came back after lunch and had screen dimming errors in the thread I'd left open
-
Not that it helps, mind.
I just reproduced a bug, and in addition to the shot of the application I took a shot of my console log in the dev tools. Not sure if that will help, but in my case there were a bunch of 429 errors sitting in there.
http://what.thedailywtf.com/t/infininoscroll/9167/9?u=boomzilla
-
-
I can't imagine how you came to that conclusion.
Well, that's probably because you're not paranoid.
-
This is what you all get for using horrible browsers. What year is it, 2007?
NOREPRO in IE11 on Windows 7
-
-
Firefox has been going downhill for the last couple years.
Google is the evil many-armed monster of the Internet and Chrome is just another one of its nasty tentacles through which it absorbs your "life force" (personal info) to feed itself.
IE is the last bastion of sane usability and privacy.
I only do backend dev so I don't care how "standards" compliant a browser is, as long as it works 99% of the time.
Standards are like toothbrushes, a good idea but no one wants to use anyone else's
Standards are like unicorns, they are pretty and wonderful, you can describe them, but you'll never actually have one you can use
-
Google is the evil many-armed monster of the Internet and Chrome is just another one of its nasty tentacles through which it absorbs your "life force" (personal info) to feed itself.
Also I do web dev. IE sucks and should die in the burning fires of a thousand supernovas.
Filed Under: I was going to do :tin_foil_hat: but we don't have one.
-
I've mostly switched to Waterfox now, it's a slightly-tweaked Firefox recompiled for 64-bit.
-
web dev
TRWTF
Seriously, web devs must be masochists. I don't know how you survive the storm-tossed sea of "standards" and new technologies. And from that perspective, I can understand why you and every other web dev hates IE and loves Chrome (and sometimes Firefox).
Market share for web developers:
But from a user's perspective, I like IE a lot more than the abominations that are Chrome and Firefox. And as a power user, even if they are not the best, the dev tools in IE11 allow me to easily manipulate the odd site now and then.
Market share for everyone else:
-
I used to mostly use Firefox (on Linux/Wndows/Android) and these days I mostly use Chrome. I have no idea why I switched...
-
I've mostly switched to Waterfox now, it's a slightly-tweaked Firefox recompiled for 64-bit.
I tend to use Nightly on my non-mobile systems:
[pjh@sofa ~]$ crontab -l 0 5 * * * /home/pjh/src/firefox/pull_build [pjh@sofa ~]$ cat ~/src/firefox/pull_build #!/bin/bash cd /home/pjh/src/firefox hg pull -vu ./mach build ./mach package [pjh@sofa ~]$
-
Firefox has been going downhill for the last couple years.
But it's a very high and flat hill!
-
I use Google. Google predominates the market obviously but occasionally I like to go to Yahoo just to give them some business.
What is a Browser? – 02:33
— Ji Lee
-
I tend to use AOL and/or Broadband...
-
But it's a very high and flat hill!
Sure, if you like 20-year-old functionalilty being ripped out just because a bunch of newbs don't understand why it's there (esc to stop image animations, for example.)
-
Also I do web dev. IE sucks and should die in the burning fires of a thousand supernovas.
tbh, ie11 is better than firefox and mostly as good as chrome at this point other than that the js performance isn't as good. The most annoying thing about IE11 is that they killed the easy-compatibility-mode-button, which was the only reason I used IE anyway... for sites that don't work in real browsers. And now if the dev hasn't gone back and put the emulate=IE7 tag in their site, they don't work in IE either without having to reload the page with the "emulation" mode on.
Every web dev over the age of 25 is the reason MS is doing "project spartan" and renaming their next browser. There is no chance they can get away from the IE stench without a full on name change.