5 ms·

Silly question, but is there any sense in testing websites in new Edge in addition to Chrome? I presume, that if website works on Chrome, it will work on Edge t

by butz 7y ago

Silly question, but is there any sense in testing websites in new Edge in addition to Chrome? I presume, that if website works on Chrome, it will work on Edge the same. Are there any gotchas in new Edge to watch out for?

gsnedders 7y ago
https://textslashplain.com/2019/05/01/edge-76-vs-edge-18-vs-chrome/ https://textslashplain.com/2019/05/01/edge-76-vs-edge-18-vs-... documents many of the differences between EdgeHTML v. Edgium v. Chrome, though it's not really that obvious skimming through what the differences between Edgium v. Chrome are (but there's a bunch, though probably things you don't need to worry about?).
jayflux 7y ago
I don’t think this question is silly at all, they are using literally the same rendering engine (it’s not a fork), it even seems to get the chromium update the same time as chrome (version numbers always match so far), so probably not, however who knows what may happen in future. The upside is that it should be easier to test with tools such as Selenium, so the lower cost of testing it may be a factor
jjeaff 7y ago
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.
- eitland 7y ago
  > 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
  - pdanpdan 7y ago
    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.
    - tallanvor 7y ago
      Sometimes it's where Firefox adheres to specifications, while Chrome doesn't. As an example, https://www.just-eat.no 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.
  - uhryks 7y ago
    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.
watersb 7y ago
`-webkit-text-size-adjust` is not applied in Edge but is supported on Google Chrome on my Windows 10 test machines. (I didn't expect size adjustment on desktop Windows 10. But my 32-bit box is a Win10 x86 tablet. Doesn't seem to be a question of "Tablet Mode".)
mr_toad 7y ago
> I presume, that if website works on Chrome, it will work on Edge the same. “Works on my machine”, said the developer, just before they took down the production environment.

by butz 7y ago

gsnedders 7y ago

https://textslashplain.com/2019/05/01/edge-76-vs-edge-18-vs-chrome/ https://textslashplain.com/2019/05/01/edge-76-vs-edge-18-vs-... documents many of the differences between EdgeHTML v. Edgium v. Chrome, though it's not really that obvious skimming through what the differences between Edgium v. Chrome are (but there's a bunch, though probably things you don't need to worry about?).

jayflux 7y ago

I don’t think this question is silly at all, they are using literally the same rendering engine (it’s not a fork), it even seems to get the chromium update the same time as chrome (version numbers always match so far), so probably not, however who knows what may happen in future. The upside is that it should be easier to test with tools such as Selenium, so the lower cost of testing it may be a factor

jjeaff 7y ago

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.

eitland 7y ago
> 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
- pdanpdan 7y ago
  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.
  - tallanvor 7y ago
    Sometimes it's where Firefox adheres to specifications, while Chrome doesn't. As an example, https://www.just-eat.no 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.
- uhryks 7y ago
  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.

watersb 7y ago

`-webkit-text-size-adjust` is not applied in Edge but is supported on Google Chrome on my Windows 10 test machines. (I didn't expect size adjustment on desktop Windows 10. But my 32-bit box is a Win10 x86 tablet. Doesn't seem to be a question of "Tablet Mode".)

mr_toad 7y ago

> I presume, that if website works on Chrome, it will work on Edge the same. “Works on my machine”, said the developer, just before they took down the production environment.