Caniuse: Make sure any feature listed as partial has related browser bug attached

Created on 6 Dec 2017 · 6Comments · Source: Fyrd/caniuse

For a number of features, a browser is listed as partial, perhaps with a description, but there is not always a browser bug logged and attached, or a test case.

For example https://caniuse.com/#feat=keyboardevent-key Edge is listed as partial but I can't really tell why. I know we had ESC rather than Escape for example, which we fixed, but the AltGr issue is vague. I spent a bunch of time testing and when switching to en-GB keyboard for example, we report Control and Alt (what it is actually mapped to in Windows). I thought maybe that is the bug but then Firefox is listed as Full Support and it does exactly the same thing, so I guess that isn't the issue. The test on https://tests.caniuse.com/?feat=keyboardevent-key passes in Edge (only tests up arrow)

DataList is another example, where it links to http://playground.onereason.eu/2013/04/ie10s-lousy-support-for-datalists/ but that is dead (and it wasn't really a list of bugs where it diverged from the spec from what I recall, some was UI behavior not specced)

As a browser dev it would be great if I can go straight to a bug so I can go and fix the issues that are impacting devs enough to be listed on CanIUse...

I'll add other features to this bug as I come across them.

Misc. sitdata request

Source

dstorey

👍2

Most helpful comment

@CendioOssman : we fixed it recently. I'm not sure if it has worked through all our various rings to the Public insider preview yet. If it doesn't work in the current insider preview, it should work in the next one.

I'll look into the AltGr issue and see what I can do. Can you do a PR for can I Use to add a JSFiddle or such showing this behaviour?

dstorey on 7 Dec 2017

🎉1 👍1

All 6 comments

Hey David, excellent points. This sounds like a good policy to have. In general I do try to ensure there's at least a note for partial support, but a bug report / test case would certainly be ideal.

Looking into the keyboardevent-key issue, I tracked that down to #3468. @CendioOssman any chance you could provide more detail here?

Fyrd on 6 Dec 2017

👍2

Sure. The problem is that Edge and IE set KeyboardEvent.key for AltrGr+\ the same as for just \. I.e. AltGr is completely ignored when setting KeyboardEvent.key. E.g. press AltGr+4 with en_GB layout and you get '4' with Edge/IE and '€' with every other browser. This forces us (noVNC) to have to wait for the legacy keypress event for those browsers.

When you fix this then please see if you can find some way for us to detect that this is indeed a fixed version of Edge/IE and not the broken one.