cool, good for you
Could you please not post unsubstantive comments to Hacker News? that's not what this site is for.
I discovered a browser bug
121–130 of 137 posts
Re: I discovered a browser bug
#122hn bet big money on firefox/mozilla? all news for other web browser is bad except firefox. HN now is mozilla's Microphone
HN doesn't bet any money on anything. Please don't post unsubstantive comments here.
Re: I discovered a browser bug
#123Another symptom of browser specs getting too complicated.
In this case it was a symptom of them being too simple. The use of range requests wasn't specified.
Re: I discovered a browser bug
#124Earlier quoted context omitted.
Personally over many bug reports and many years: A+ experience with the Chrome team E with Edge F with Safari The Chrome devs have been astonishingly good. My experience has repeatably been that if they are given a good bug report, they get it fixed and often fix it really fast. Or they reply with excellent technical reasons why not. Also multiple times I have seen extreme corner-case regressions get magically fixed…
Apple hears ya, Apple don't care.
Yeah apparently from people familiar with the deep black hole that is Radar you're supposed to keep submitting bugs, dupes count as a vote or something.
It sounds absolutely horrendous.
Re: I discovered a browser bug
#125Earlier quoted context omitted.
Absolutely, there should be a different port for web pages than applications. Even if we started by disabling js on port 80
That's a complete non-starter as long as advertising pays for the web pages. Or even longer, if the replacement compensation methods require JS as well.
Maybe there would be less money in it, but it is possible to do advertising completely on the backend as well. You send the advertiser some targeting info, e.g.: what does the article(s) on the page talk about, what is your site about, what is an estimated profile of your readers, and the ad network gives you the ad images and text in some nice format.
Yes, it does require confidence that the publisher will actually show your ad, but it was the same thing for the journals. On the web you can still track outgoing links and have the referer, so you can know the actual impact of your ads anyways.
Re: I discovered a browser bug
#126Earlier quoted context omitted.
What about differentiating applications and web sites? The line between the two is blurry, I know, but I would be happy if the document metaphor were divorced from the application one.
Absolutely, there should be a different port for web pages than applications. Even if we started by disabling js on port 80
how about 80 vs 443? :)
Re: I discovered a browser bug
#127Earlier quoted context omitted.
> If anyone runs into problems like this, feel free to bug one of the Chrome dev rel folks, such as me. Hi, and thanks for being part of creating Chrome && reaching out here. Now that I have a Chrome guy here maybe you can help with another annoying issues: -QC internally at Google seems to be blissfully unaware of the fact that other browsers exists. Examples: - one glaring issue I'm running into in core Angular on…
And this is why you don't get immediate access to a dev folks!
I have direct access to Mozilla devs. Look how much I bother them.
Re: I discovered a browser bug
#128I can echo his experience reporting browser bugs and provide my own reviews: Firefox - By far the best. Quick response, usually from engineers. If it's important the fix will be quick. Edge - No reply for months / years. When I've gotten replies back it's been to ask me to try with the current version. When I do and the bug still exists it goes back at the bottom of the queue it seems. Chrome - Somewhat of a mixed ba…
Personally over many bug reports and many years: A+ experience with the Chrome team E with Edge F with Safari The Chrome devs have been astonishingly good. My experience has repeatably been that if they are given a good bug report, they get it fixed and often fix it really fast. Or they reply with excellent technical reasons why not. Also multiple times I have seen extreme corner-case regressions get magically fixed…
I once reported a chrome issue. Got no attention until I found a different issue I thought was related and commented there, which got the attention of someone competent who realized it was a hardware bug they'd fixed before but had a regression.
Not a security bug, just that a very large number of websites didn't load.
Re: I discovered a browser bug
#129Earlier quoted context omitted.
What would you rather happen? Browser vendors hire more people such that they can fix every valid bug ever filed?
Maybe. A first good step would be if the billion dollar company would try to come up to the standard of the non profit.
*trillion dollar company.
Re: I discovered a browser bug
#130Earlier quoted context omitted.
One can see a rationale in not having a security group - every team should have security focus (eg by having expertise & champions within each group). You can't tack on security, you have to build it in.
I think you need both. Same as I think you need i10n and a8y at both layers.
Uhhh...what are i10n and a8y?