Open Bug 1623290 Opened 5 years ago Updated 2 years ago

Add `ChromeOnly` to Selection.webidl's `caretBidiLevel`, or standarize it

Categories

(Core :: DOM: Selection, enhancement)

Product:
Core
Component:
DOM: Selection
Type:
enhancement

Tracking

()

People

(Reporter: mbrodesser-Igalia, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

It's neither part of the spec nor exposed by Chrome.

I just spotted this too while looking for non-standard things to cover in http://mdn-bcd-collector.appspot.com/.

Does this ever return anything other than null?

(In reply to Philip Jägenstedt [:foolip] from comment #1)

I just spotted this too while looking for non-standard things to cover in http://mdn-bcd-collector.appspot.com/.

Does this ever return anything other than null?

Yes. For instance 0 and 1 are possible. One can reproduce that for instance with the text of https://github.com/ProseMirror/prosemirror/issues/960#issue-474013365.

Blocks: proprietary-dom

Does this need a use counter before removal?

It seems like it's six years old, was added in bug 1067788, and was supposed to be ChromeOnly? Sigh. I suspect putting it behind a flag for a couple Nightly/early Beta cycles is sufficient, but sending an intent to unship to see if anyone wants a counter would be good.

It seems this test is the only use of the attribute. It doesn't sound like a very good reason to keep it at all, maybe we could just remove it and modify the test 🤔

Edit: I guess https://github.com/ProseMirror/prosemirror/issues/960 needs to be investigated so that it won't regress by the removal.

Yeah maybe, it was added for B2G... I do think we should do it somewhat gradually though, i.e., with a flag.

Assignee: nobody → krosylight

I think we need this feature, based on :jfkthame's explanation.

URL: https://github.com/w3c/selection-api/...
Summary: Add `ChromeOnly` to Selection.webidl's `caretBidiLevel` → Add `ChromeOnly` to Selection.webidl's `caretBidiLevel`, or standarize it

Not doing this for now. I think removing this is not very plausible for now.

Assignee: krosylight → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.