Hacker News Reader

Comment by jjeaff | Hacker News Reader

I'm sure there may be some small differences that may require some testing, but I am already starting to phase out some of my edge browser testing and looking forward to no longer supporting pre-chromium edge. We already don't support IE and haven't for 5 years.

Just testing for Firefox and chrome/edge will be nice.

View on HN

> Just testing for Firefox and chrome/edge will be nice.

Thanks! Most thinks just work on Firefox but I also see a number of things not working because certain people just can't be bothered to:

a) learn to not use Chrome-specific hacks instead of the normal way

b) just test their sites with the second most used browser engine

Hello. Can you please give some examples of Chrome-specific hacks instead of the normal way, or some web references. I'm helping on development of a web UI framework and it would help. Thank you.

Sometimes it's where Firefox adheres to specifications, while Chrome doesn't.

As an example, https://www.just-eat.no

Chrome treats the numeric box as text and accepts a postcode starting with 0. Firefox correctly implements the numeric type, which unfortunately makes the site unusable for all Firefox users in Oslo.

They get none of my business because I'm not willing to switch to Chrome just to order from them.

I'm a happy FF user but let's be honest here, the second most used browser engine is Webkit (especially on iOS), far ahead of FF.

Reply on news.ycombinator.com