4 ms·

See also this https://mobile.twitter.com/frivoal/status/1015441793901477888 https://mobile.twitter.com/frivoal/status/101544179390147788...

• Sniffnoy 8y ago
  Non-mobile link: https://twitter.com/frivoal/status/1015441793901477888 https://twitter.com/frivoal/status/1015441793901477888
• bfrydl 8y ago
  I think one of the most optimistic things to notice about these two images is that Edge amazingly appears to be correct in both cases.
  • PeCaN 8y ago
    It's pretty clear that Microsoft really took a close look at the specs when developing Edge, which is really nice. It also has the benefit of being the newest of the major engines.
    • chrismorgan 8y ago
      Actually, much of the time it comes down to what bugs people report. In a closely related area, IE and Edge both added spread distance rather than subtracting it on inner box-shadows until I reported it last year, then it was fixed in IE within a month: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12515080/ https://developer.microsoft.com/en-us/microsoft-edge/platfor.... In this particular case, they may have got the best of it because IE didn’t support outline-offset at all, and so when they implemented it they read the spec carefully. Edge is a continuation of IE. Large swathes of the renderer have been rewritten, but when you do find bugs in Edge they’re commonly shared with IE.
      • chrismorgan 8y ago
        (Correction: fixed in Edge within a month; IE doesn’t get such fixes. Also “IE and Edge both” should read “both IE and Edge” for increased clarity.)
• gsnedders 8y ago
  Note that Florian is the editor of CSS UI, which defines the outline properties, where all this unspecified behaviour exists (mostly because browser vendors don't really care enough to make outline interoperable).