Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WebKit Quirks

github.com

Post reply on HN
Print view View original

1–10 of 91 posts

Re: WebKit Quirks

#3

Post by robin_reala »

sdflhasjd wrote: post #2

Domain name specific quirks? What in the world...

Oh, WebKit are absolutely not the only people doing this. Opera used to with their Presto engine, and I’m pretty sure I’ve seen a similar list in Gecko, though I can’t find it now.

At the end of the day, this is the only way that non-Chrome browsers can meet Google’s hegemony, unless they give up and adopt Chromium itself. The opportunity cost of switching is too low for browser manufacturers no to have these workarounds; if a site is broken for a user, then they’ll change browser.

Re: WebKit Quirks

#4

Post by sdflhasjd »

robin_reala wrote: post #3
sdflhasjd wrote: post #2

Domain name specific quirks? What in the world...

Oh, WebKit are absolutely not the only people doing this. Opera used to with their Presto engine, and I’m pretty sure I’ve seen a similar list in Gecko, though I can’t find it now. At the end of the day, this is the only way that non-Chrome browsers can meet Google’s hegemony, unless they give up and adopt Chromium itself. The opportunity cost of switching is too low for browser manufacturers no to have these workaro…

Yes, it is a real shame, but then again, a lot of these sites are made by reasonably big companies.

I'm sure trello and such could fix whatever these input quirks are.

Then there's autoplay specific behaviour on facebook, twitter and netflix. Is this really a google hegemony thing, or is this leniency that other sites don't get?

I'm just trying to see if there's similar examples in Blink & Gecko right now.

Re: WebKit Quirks

#6

Post by 0x0 »

I bet it's fun being responsible for developing and deploying on those sites. Works in CI and dev, but deploying to production makes the browser behave differently! Nice surprise!

Re: WebKit Quirks

#7

Post by robin_reala »

sdflhasjd wrote: post #4
robin_reala wrote: post #3

Earlier quoted context omitted.

Oh, WebKit are absolutely not the only people doing this. Opera used to with their Presto engine, and I’m pretty sure I’ve seen a similar list in Gecko, though I can’t find it now. At the end of the day, this is the only way that non-Chrome browsers can meet Google’s hegemony, unless they give up and adopt Chromium itself. The opportunity cost of switching is too low for browser manufacturers no to have these workaro…

Yes, it is a real shame, but then again, a lot of these sites are made by reasonably big companies. I'm sure trello and such could fix whatever these input quirks are. Then there's autoplay specific behaviour on facebook, twitter and netflix. Is this really a google hegemony thing, or is this leniency that other sites don't get? I'm just trying to see if there's similar examples in Blink & Gecko right now.

I work for a big company. There have been plenty of outstanding bugs in my company’s sites and apps, because the people that care aren’t in teams that own the systems with bugs in, or aren’t in a position to have their voices heard, and that’s before the hydra of ”legacy software” rears its many-consultanted head.

(at least in my org we’re generally better at this now)

Re: WebKit Quirks

#8

Post by erichurkman »

sdflhasjd wrote: post #4
robin_reala wrote: post #3

Earlier quoted context omitted.

Oh, WebKit are absolutely not the only people doing this. Opera used to with their Presto engine, and I’m pretty sure I’ve seen a similar list in Gecko, though I can’t find it now. At the end of the day, this is the only way that non-Chrome browsers can meet Google’s hegemony, unless they give up and adopt Chromium itself. The opportunity cost of switching is too low for browser manufacturers no to have these workaro…

Yes, it is a real shame, but then again, a lot of these sites are made by reasonably big companies. I'm sure trello and such could fix whatever these input quirks are. Then there's autoplay specific behaviour on facebook, twitter and netflix. Is this really a google hegemony thing, or is this leniency that other sites don't get? I'm just trying to see if there's similar examples in Blink & Gecko right now.

> if (host == "trailers.apple.com")

> return true;

Even Apple themselves are not immune.

Re: WebKit Quirks

#10

Post by TonyTrapp »

I really dislike this sort of quirk workarounds, not just in web browsers. It just makes everything complicated. Someone else using the exact same code will get different behaviour, just because they serve it from a different domain. I did similar workarounds before (not related to websites but to specific files), and I felt very bad about it even though it was clear that no more files in that specific format would ever be generated again.
Post reply on HN