On Wed, 4 Dec 2013, Ryosuke Niwa wrote:
Now that I've implemented the new behavior in WebKit, I'm not certain
completely ignoring the form element pointer is the right behavior here.
That would mean that we'll allow nested form elements and isindex
element will create its own form element
On Dec 5, 2013, at 8:28 AM, Ian Hickson i...@hixie.ch wrote:
On Wed, 4 Dec 2013, Ryosuke Niwa wrote:
Now that I've implemented the new behavior in WebKit, I'm not certain
completely ignoring the form element pointer is the right behavior here.
That would mean that we'll allow nested form
A bigger issue with CSS, HTML too seems to suffer from spec
fragmentation. I’m explaining my perspective on the problem and
options in the following place simply because of the unique setup of
the different groups working on HTML and CSS:
http://meiert.com/en/blog/20131205/spec-fragmentation/
I
On Thu, 21 Nov 2013, Ryosuke Niwa wrote:
A start tag whose tag name is isindex
http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#isindex
Right now, form element pointer is not null in the following example, so we
end up losing isindex element entirely.
On Dec 5, 2013, at 8:36 AM, Ryosuke Niwa rn...@apple.com wrote:
On Dec 5, 2013, at 8:28 AM, Ian Hickson i...@hixie.ch wrote:
On Wed, 4 Dec 2013, Ryosuke Niwa wrote:
Now that I've implemented the new behavior in WebKit, I'm not certain
completely ignoring the form element pointer is the
On Thu, Dec 5, 2013 at 5:30 AM, Ian Hickson i...@hixie.ch wrote:
On Tue, 3 Dec 2013, Dimitri Glazkov wrote:
Yeah, the idea is you'd bind to the scroll box to change the whole
scroll UI, but you could also then override specific pseudos of the
scroll box to style subparts of the
On Tue, 22 Oct 2013, Bruno Racineux wrote:
article is fine for a comment as syndicate-able and self-contained.
Even a LOL comment. People often publish full articles that are far
less useful or intelligible comment that a LOL. I just wish it was art.
It's probably too late to change the
On Wed, 04 Dec 2013 16:12:50 -, TJ VanToll tj.vant...@gmail.com
wrote:
The datepicker also shows the problem that using pseudo-elements as
styling hooks presents. The calendars presented on mobile browsers and
desktop browsers are radically different. Even if you wanted to
On Fri, Dec 6, 2013 at 2:01 AM, Kornel Lesiński kor...@geekhood.net wrote:
Maybe instead of coming up with one set of pseudo-elements that's limited to
the lowest common denominator we should have multiple completely different
sets of pseudo-elements for each kind of interface?
Our Google Japan members working around IME discussed about inputmode.
Proposal:
Remove kana, katakana and full-width-latin from inputmode attribute.
Because above attributes and others are independent as others say.
For web developers that want to manage IME state like native applications,
the
10 matches
Mail list logo
