I discovered a browser bug • Hacker News Board

Re: I discovered a browser bug

#101

Post by z3t4 » Thu, Jun 21, 2018, 10:04 PM UTC

obl wrote: post #2

It's quite incredible how the web managed to get along with such a janky sandbox model. It's a very important thing that users trust their browser and won't hesitate a second to enter an unknown URL. They see "going to a webpage" as the equivalent to looking at a poster in the street, not eating candy provided by a random stranger. Eroding this trust would ruin it for everyone, even well behaved static websites witho…

Some browsers allow you to have many profiles. So you can use one profile for banking and e-mail, and another profile when browsing dubious sites.

Re: I discovered a browser bug

#102

Post by thefifthsetpin » Thu, Jun 21, 2018, 10:09 PM UTC

reitanqild wrote: post #98

notatoad wrote: post #90

Earlier quoted context omitted.

well thanks for doing your best to ensure they stop engaging on HN, i guess...

Tell me a better way to get Google to fix things, I'm all ears. Complaining in social media, bugging people you know inside the walls and calling them out here works

You have the wrong attitude here. Twice, actually.

The fact that you haven't found a good way to get Google to fix things for you isn't an excuse to just charge forward with the best way that you have found.

Suppose you're stuck in traffic. The most effective way to move forward might really be to just lay on your horn. The people in front of you will probably eventually yield (most just eager to put distance between themselves & you, others generously assuming that you have some kind of emergency). That doesn't make it okay for you to do that.

The second time you had the wrong attitude is when you demanded that people teach you a better way. Maybe somebody on HN will generously extend that favor to you, but if they do then realize that they've done you a favor -- they didn't owe it to you.

Re: I discovered a browser bug

#103

Post by oblio » Thu, Jun 21, 2018, 10:15 PM UTC

contras1970 wrote: post #80

oblio wrote: post #67

Earlier quoted context omitted.

> The single greatest web innovation in the last 30 years was readability mode. For you. From what I see, everyone else seems to be enjoying the dancing and singing monkeys online.

the monkeys[1] are enjoying themselves, dancing and singing, at the expense of everybody else. [1] web application pushers edit: hn "syntax"

By monkeys I meant literal monkeys, animations and videos and games and generally “frivolous” features.

Re: I discovered a browser bug

#104

Post by cbr » Thu, Jun 21, 2018, 10:29 PM UTC

joshschreuder wrote: post #100

WorkLifeBalance wrote: post #6

Earlier quoted context omitted.

Do you want to reinforce established monopolies? Because I can't think of a better way of doing that than having a technical difference between "trusted" and "untrusted" sites.

Aren't we sort of starting down that path already? IIRC Chrome only allows certain operations on HTTPS domains as of late such as webcam or microphone access. It seems like this sort of iterative securing of different things over time could be a good way to secure the web while also giving time for older sites to upgrade.

Anyone can get an HTTPS cert, and with Let's Encrypt it's free. Restricting dangerous features to only websites that can demonstrate their traffic hasn't been man-in-the-middled is very different from giving established sites more expansive permissions.

(Disclosure: I work at Google, though not on browsers)

Re: I discovered a browser bug

#105

Post by zamalek » Thu, Jun 21, 2018, 11:00 PM UTC

evfanknitram wrote: post #61

zegl wrote: post #44

Microsoft claims to be developer friendly these days, but they are clearly not white-hat friendly.

My entirely anecdotal experience is that they are white-hat friendly some time. My last experience was super good.

I think it depends on the team.

Re: I discovered a browser bug

#106

Post by jjcm » Thu, Jun 21, 2018, 11:14 PM UTC

forgot-my-pw wrote: post #79

_trampeltier wrote: post #22

Earlier quoted context omitted.

The PDF was great too ;-)

lol no

For people downvoting forgot-my-pw, "lol no" was the complete content of the pdf.

Re: I discovered a browser bug

#107

Post by WiseWeasel » Thu, Jun 21, 2018, 11:37 PM UTC

philipwhiuk wrote: post #76

pbhjpbhj wrote: post #46

Earlier 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.

A8y? That can't be a thing... if it is, we should put a stop to it. axb maybe?

Re: I discovered a browser bug

#108

Post by hnruss » Thu, Jun 21, 2018, 11:55 PM UTC

I've found a couple of browser bugs in different browsers (but nothing security-related). Nothing I've reported to browser teams has ever been fixed, even with simple standalone test cases. It's definitely easier just to write a workaround and call it good.

Re: I discovered a browser bug

#109

Post by amelius » Fri, Jun 22, 2018, 12:13 AM UTC

Another symptom of browser specs getting too complicated.

Re: I discovered a browser bug

#110

Post by userbinator » Fri, Jun 22, 2018, 12:19 AM UTC

MatthewPhillips wrote: post #28

I 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…

In other words, the experience gets progressively worse the bigger the company. I'm not surprised, having worked in companies of that scale the amount of bureaucracy and general red-tape to do the smallest of things is absolutely irritating.