On Fri, 05 Aug 2011 02:31:10 +0200, Ryosuke Niwa rn...@webkit.org wrote:
Not sure. This happens all the time in design mode. We've had plenty of
crash reports that only reproduce when there are no document element.
It might also be hard to implement such a behavior in WebKit at least
because
On Fri, Aug 5, 2011 at 1:57 AM, Jonas Sicking jo...@sicking.cc wrote:
It would make sense to me to match ES here. The main concern is of
course website compat. Could someone detail what the differences would
be compared to what implementations/the HTML5 spec do now?
As far as I know, the only
On Fri, Aug 5, 2011 at 9:57 AM, Jonas Sicking jo...@sicking.cc wrote:
Why treat documentElement specially here? Just make the documentElement
*not* have a undoManager by default and have it just use it's ancestor's,
just like all other elements.
The document is an ancestor of the
On Fri, Aug 5, 2011 at 10:01 AM, Ryosuke Niwa rn...@webkit.org wrote:
On Fri, Aug 5, 2011 at 9:57 AM, Jonas Sicking jo...@sicking.cc wrote:
Why treat documentElement specially here? Just make the documentElement
*not* have a undoManager by default and have it just use it's ancestor's,
just
The current description of draw*FocusRing does not have inform the
user in the correct priority.
It currently follows cases where the user should be informed, but the
steps have been aborted.
Please review the following an provide feedback. This attempts to serve
the use cases put
forward for
On Thu, Aug 4, 2011 at 5:22 PM, Ryosuke Niwa rn...@webkit.org wrote:
I see. It's an interesting point. In WebKit, we're quite inconsistent in
relying on CSS/rendering engine and pure DOM. This is an inherent issue in
RTE because user would like the editor to work like WYSIWYG yet we have to
Why is there a need for a 'reapply' action? How is it different from
the 'apply' action?
In the case of collaborative editing apps, reapply is different from apply
because the backend server may have a tree of transaction history and may
need to consult on demand in order to determine
On Fri, Aug 5, 2011 at 1:59 PM, Jonas Sicking jo...@sicking.cc wrote:
In the case of collaborative editing apps, reapply is different from
apply because the backend server may have a tree of transaction history and
may need to consult on demand in order to determine exactly what mutations
2011/8/3 Kornel Lesiński kor...@geekhood.net:
On Wed, 03 Aug 2011 16:26:41 +0100, Tab Atkins Jr. jackalm...@gmail.com
wrote:
What do you think?
Implementing this seems rather complicated for such a niche use. It also
seems better to let sites handle this by themselves so these physical
On Tue, Aug 2, 2011 at 8:31 PM, Ryosuke Niwa rn...@webkit.org wrote:
I've read a part of sections 7 and 8 but I've kind of lost here. The spec
is very detailed and I can't really get a high-level view of what will
happen. It might be helpful to have some high-level summary of what it
tries
On Fri, Aug 5, 2011 at 2:40 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Fri, Aug 5, 2011 at 1:59 PM, Jonas Sicking jo...@sicking.cc wrote:
In the case of collaborative editing apps, reapply is different from
apply because the backend server may have a tree of transaction history and
may
On Fri, Aug 5, 2011 at 8:43 AM, Aryeh Gregor a...@aryeh.name wrote:
On Fri, Aug 5, 2011 at 1:57 AM, Jonas Sicking jo...@sicking.cc wrote:
It would make sense to me to match ES here. The main concern is of
course website compat. Could someone detail what the differences would
be compared to
On Fri, Aug 5, 2011 at 5:06 PM, Jonas Sicking jo...@sicking.cc wrote:
Though I guess you can always supply the same function for apply and
reapply, but that means you can't use the convenient inline syntax
that you've used in your examples.
Or does 'reapply' default to the 'apply' function
On Fri, Aug 5, 2011 at 5:17 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Fri, Aug 5, 2011 at 5:06 PM, Jonas Sicking jo...@sicking.cc wrote:
For example in the collaborative editing case I would think that the
page generally wants to get a semantic understanding of the editing
operations so that
Aryeh Gregor a...@aryeh.name, 2011-08-04 14:22 -0400:
On Wed, Aug 3, 2011 at 5:06 PM, Ehsan Akhgari eh...@mozilla.com wrote:
Is it possible to get a unique QA contact (or default CC address) for this
component please, so that people who are interested in watching it can watch
that email
15 matches
Mail list logo
