On Fri, 05 Aug 2011 22:57:13 +0200, Aryeh Gregor a...@aryeh.name wrote:
Yeah, it all looks the same to the user, so I don't see why
visibility: hidden should be any different. Just let the user select
and manipulate the hidden text like any other text.
Things that are visibility:hidden are
On Mon, Aug 8, 2011 at 5:03 AM, Simon Pieters sim...@opera.com wrote:
Things that are visibility:hidden are not focusable. I don't think that can
be changed without compat problems. If visibility:hidden things are not
focusable, I guess it makes sense to not make it selectable, too. (Possibly
On 11-08-06 1:33 AM, Michael[tm] Smith wrote:
Aryeh Gregora...@aryeh.name, 2011-08-04 14:22 -0400:
On Wed, Aug 3, 2011 at 5:06 PM, Ehsan Akhgarieh...@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
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
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
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
On Wed, Aug 3, 2011 at 5:06 PM, Ehsan Akhgari eh...@mozilla.com wrote:
On 11-08-03 4:13 PM, Aryeh Gregor wrote:
Mike Smith has been kind enough to add a component to the W3C Bugzilla
for the editing spec, in the WebApps WG product. From now on I'll use
it for tracking feedback so I can be
On Wed, Aug 3, 2011 at 1:13 PM, Aryeh Gregor a...@aryeh.name wrote:
On Tue, Aug 2, 2011 at 8:31 PM, Ryosuke Niwa rn...@webkit.org wrote:
Feedback on selections 5 through 7:
The definition of collapsed line break isn't clear. Maybe it's br
immediately before the end of a block?
Here's my feedback on sections 1-3. I'll provide feedback on the rest
of the specification in the near future.
3.2
* The gecko prefix should be changed to moz, to be compatible with
other Gecko specific prefixes.
* Do we have any other case where the HTML spec says that a browser can
change
Mike Smith has been kind enough to add a component to the W3C Bugzilla
for the editing spec, in the WebApps WG product. From now on I'll use
it for tracking feedback so I can be organized about things that I
can't fix right away. The link to file a bug is:
On Tue, Jul 26, 2011 at 5:26 PM, Aryeh Gregor simetrical+...@gmail.com wrote:
Anyone reviewing the spec should be advised that I put extensive
rationale in HTML comments. If you want to know why the spec says
what it does, check the HTML source. I plan to change this to use
details or such
On Wed, Jul 27, 2011 at 4:51 PM, Ryosuke Niwa rn...@webkit.org wrote:
Feedback on sections 1 through 3:
- WebKit treats any font-weight above or equal to 600 as bold because
that's what user sees, and boldness is a binary concept in execCommand;
Firefox 5 appears to do the same.
On Thu, 28 Jul 2011 01:51:31 +0200, Ryosuke Niwa rn...@webkit.org wrote:
The return value of queryCommandEnable depends on beforecut, beforecopy,
and beforepaste events and selection state in WebKit;
This is actually a use case for before* events I wasn't aware of.
Interesting. I guess
On Wed, Jul 27, 2011 at 7:51 PM, Ryosuke Niwa rn...@webkit.org wrote:
WebKit treats any font-weight above or equal to 600 as bold because that's
what user sees, and boldness is a binary concept in execCommand; Firefox 5
appears to do the same.
WebKit compares colors in rgb/rgba format; e.g.
Thanks to both of you for the feedback!
On Wed, Jul 27, 2011 at 7:51 PM, Ryosuke Niwa rn...@webkit.org wrote:
WebKit treats any font-weight above or equal to 600 as bold because that's
what user sees, and boldness is a binary concept in execCommand; Firefox 5
appears to do the same.
Yes, bold
On Thu, Jul 28, 2011 at 1:17 PM, Aryeh Gregor simetrical+...@gmail.comwrote:
3.3: The return value of queryCommandEnable depends on beforecut,
beforecopy, and beforepaste events and selection state in WebKit; WebKit
returns false if default actions are prevented in those events or
Feedback on sections 1 through 3:
- WebKit treats any font-weight above or equal to 600 as bold because
that's what user sees, and boldness is a binary concept in execCommand;
Firefox 5 appears to do the same.
- WebKit compares colors in rgb/rgba format; e.g. red is first parsed as
Since February, I've been working on writing a detailed specification
for browser editing, primarily the document.execCommand() and
document.queryCommand*() methods. These were created by Microsoft in
the 1990s and were subsequently adopted in some form by all other
browsers, and today browsers
18 matches
Mail list logo
