[whatwg] WF2: Informative style sheet appendix?

CSS 2 provides in Appendix A, and CSS 2.1 in Appendix D, non-normative references which implementers may use as a basis for styling HTML pages by default. Web Forms 2 is missing a similar style sheet for all the new features it brings to the table. For example, on my XUL Widgets project I have

[whatwg] Web Forms 2.0 in Gecko design document

For anyone interested in seeing WF2 implemented in mozilla.org code, I invite you to read and comment on http://wiki.mozilla.org/DOM:Web_Forms_2.0 . Please bear in mind this is intended as an internal design document, and this is very much a first draft - so it will change! -- The first step in

[whatwg] WF2: required attribute clarification requested

For disabled or readonly controls, the (required) attribute has no effect. What does this mean? The missingValue bit of validityState is either on or off. Do I need to change the required bit if we're disabled? Or should I leave it alone? -- The first step in confirming there is a bug in

[whatwg] WF2: Clarification on valueMissing requested

events? Both, or some other way? I'm working from the DOM events view right now, and this could be the difference between dispatching one event and dispatching many. I don't require an immediate answer. Forgive me if the questions above have already been raised and discussed. Alex Vincent

[whatwg] WF2 clarification request: File upload controls

In the past, user agents have allowed file upload controls to reference files not local to the computer in question. For validity purposes, I wonder if this should still be allowed under Web Forms 2.0. Allowing remote values in the file upload control could be a performance hit via networking,

[whatwg] Text areas with pattern attributes?

I'm drifting into writing code for the pattern attribute on text fields again, and I wondered:  if text inputs can have pattern attribute for regular expression matching, why not text area elements? The HTML 5 spec says: The textarea element represents a multiline plain text edit control for the

Re: [whatwg] Text areas with pattern attributes?

On Mon, Aug 24, 2009 at 6:04 AM, Max Romantschukm...@romantschuk.fi wrote: I really don't see a case for not allowing pattern for a textarea. The implementation side should not be that different from the same attribute on a text input? Except for the client side overhead of parsing a large

[whatwg] HTML 5 clarifications on ValidityState?

I read this paragraph (from section 4.10.15.3) as self-contradicting: The validationMessage attribute must return the empty string if the element is not a candidate for constraint validation or if it is one but it satisfies its constraints; otherwise, it must return a suitably localized message

[whatwg] HTML 5 buttons and constraint validation

There's a possible disconnect between input type=button/ and button/. The former is barred from constraint validation, but the latter is not. (Section 4.10). Is this intentional? -- The first step in confirming there is a bug in someone else's work is confirming there are no bugs in your own.

[whatwg] DOM mutations, transactions and UndoManager thoughts

on the UndoManager section, and on undo/redo operations in general, with this e-mail. Alex Vincent San Leandro, CA author, Verbosio XML editor project (in development hell for six years and counting!) -- The first step in confirming there is a bug in someone else's work is confirming there are no bugs

[whatwg] input type=password... restrict reading value from JS?

This is just an idea. For the last 10+ years, password inputs have been accessible from scripts, with nary a complaint. If I have this code: form action=javascript:void div input type=password id=pw button onclick=alert(document.getElementById('pw').value)Show password!/button

Re: [whatwg] input type=password... restrict reading value from JS?

On Sun, Jul 10, 2011 at 3:21 AM, Michal Zalewski lcam...@coredump.cxwrote: For the last 10+ years, password inputs have been accessible from scripts, with nary a complaint. If I have this code: Unfortunately, the problem is not that easy to fix: denying access to the field does not

Re: [whatwg] Fixing undo on the Web - UndoManager and Transaction

In the last couple of weeks, I've been working with developers of CKEditor, TinyMCE, and Google Docs to come up with *new API for undo and redo*. I'd like to take a look at this and be very closely involved in this specification. About a month ago, I wrote this:

Re: [whatwg] DOM mutations, transactions and UndoManager thoughts

Thanks, Ian. I've been loosely following the UndoManager discussion - reading all the e-mails coming through. I haven't thought about it for a couple weeks, though. I'll take another look at the current draft soon. I'll need some time to come back to mutation events. Alex On Fri, Aug 26,

Re: [whatwg] Fixing undo on the Web - UndoManager and Transaction

There's too much good stuff going on, both in the specs, and in my own project. :-) I noticed Ehsan's blog post about editing on the Web, http://ehsanakhgari.org/blog/2011-08-31/future-editing-web . I'm groaning because I haven't been involved! :-p A few thoughts on my mind: 1. I think we

Re: [whatwg] Fixing undo on the Web - UndoManager and Transaction

On Thu, Sep 1, 2011 at 11:36 AM, Ryosuke Niwa rn...@webkit.org wrote: On Thu, Sep 1, 2011 at 6:26 AM, Alex Vincent ajvinc...@gmail.com wrote: 1. I think we should start writing a test suite, for two reasons. First, to get some idea how this works in practice, with a reference

[whatwg] UndoManager questions

Hi, folks. I'm stubbing out a quick dirty implementation of UndoManager in JavaScript, and I have a few questions. For those not familiar, the spec lives here: http://rniwa.com/editing/undomanager.html * The spec is inconsistent in a few places. For instance, in the green non-normative

Re: [whatwg] Exceptions in UndoManager

My first concern is what state will the UndoManager be in when an exception happens? There may be transactions that were undone, cropped off On Wed, May 30, 2012 at 12:03 AM, Ryosuke Niwa rn...@webkit.org wrote: When an exception is thrown within transact(), the most sane behavior appears to

Re: [whatwg] Exceptions in UndoManager

Sorry, I hit send prematurely. Let me try again in a few minutes. On Wed, May 30, 2012 at 8:15 AM, Alex Vincent ajvinc...@gmail.com wrote: My first concern is what state will the UndoManager be in when an exception happens? There may be transactions that were undone, cropped off On Wed

Re: [whatwg] Exceptions in UndoManager

1. What state will the UndoManager be in when an exception happens? There may be transactions that were undone, cropped off by the transact() call, which per the spec are now unrecoverable. Also, in the undo or redo cases, we might be in the middle of a merged transaction. The spec

[whatwg] Verbosio 'template DOM' - breaking the rules for a reason

to others in this space. The project's code is available under the Mozilla Public License version 2. Alex Vincent Hayward, CA, U.S.A. Planet Earth, Milky Way Galaxy, the Universe (roughly) -- The first step in confirming there is a bug in someone else's work is confirming there are no bugs in your own

[whatwg] HTML inputs directly toggling CSS classes on elements?

A few days ago, I dipped my toes into web design again for the first time in a while. One of the results is the CSSClassToggleHandler constructor from [1]. Basically, it takes an radio button or checkbox, and turns that input into a toggle for a CSS class on another element. This is relatively