Open Bug 931495 Opened 9 years ago Updated 2 months ago
IAnonymous Content Creator API
For creating a touch-friendly cursor handle on Firefox OS, we are going to implement it as a couple of native anonymous elements per discussion with Ehsan.
Which frames are going to have the anonymous content? (I'm not sure "CSS Parsing and Computation" is the right component for this btw.)
Currently, the <table> and <img> frames will have anonymous content while in editor mode. We are going to append the cursor handle on any selectable frame. Based on https://bugzilla.mozilla.org/show_bug.cgi?id=439258#c45, it should be literally any frame. I don't know the correct component either, so I just copy it from bug 439258.
blocking-b2g: --- → 1.3+
Target Milestone: --- → 1.3 Sprint 5 - 11/22
Ehsan, we talked at the summit about doing this by overlaying handles over the top of the content, not by creating anonymous children. What changed?
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #3) > Ehsan, we talked at the summit about doing this by overlaying handles over > the top of the content, not by creating anonymous children. What changed? I changed my mind, since that would be a pure gaia hack, which we won't be able to use for Firefox for Metro/Android...
We could put the overlay handles in Gecko, which would let us share code easily and keep the other advantages of overlaying handles, namely not having to support anonymous children for every single kind of frame, and having the selection handles not be affected by opacity, filters, transforms and other effects.
OK, that's fair. (Note that we're also discussing this over in bug 924692.)
Remove block on 921964 and 924692 because the cursor movement no longer uses API for the implementation. According to the engineer's discussion, we will use the existing objective to implement the cursor movement. As a result, remove 1.3 flag as well because this is no longer a blocker for cursor movement feature in v1.3.
You need to log in before you can comment on or make changes to this bug.