David Carlisle on Fri, 18 Jan 2013 00:03:12 +:
> To: Ian Hickson
> On 17/01/2013 23:31, Ian Hickson wrote:
>> On Thu, 17 Jan 2013, David Carlisle wrote:
> that documents will be interpreted differently by an XHTML
> user agent and a standard XML toolchain.
I do not understa
On 17/01/2013 23:31, Ian Hickson wrote:
On Thu, 17 Jan 2013, David Carlisle wrote:
http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html
But basically it solves the problem that the existing list leads to
a situation where data corruption and user confusion are both
inevitable as the only wa
On Thu, 17 Jan 2013, David Carlisle wrote:
>
> http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html
>
> But basically it solves the problem that the existing list leads to a
> situation where data corruption and user confusion are both inevitable
> as the only way to enable entities to be lo
All,
so after talking to Dirk, maybe it's better to rename the classes so Path
is the one that has the geometry and StyledPath contains the region.
Prototype IDL:
[Constructor,
Constructor(path), // creates a copy
Constructor(DOMString)] //takes SVG path syntax
interface Path {
};
Path impleme
On Fri, 7 Dec 2012, Matt Falkenhagen wrote:
>
> How are cycles with magically aligned elements resolved?
>
> For example, if a and b are dialogs and you do:
>
> a.show(b);
> b.show(a);
>
> I think an anchoring cycle can also occur if an element |a| is anchored
> to a descendent of an element anc
On 17/01/2013 18:58, Ian Hickson wrote:
On Thu, 17 Jan 2013, David Carlisle wrote:
By adding
"-//W3C//ENTITIES HTML MathML Set//EN//XML"
To the list in
13.2 Parsing XHTML documents
Of Identifiers that are recognised when parsing XHTML syntax documents.
What problem does this solve?
We t
On Fri, 7 Dec 2012, Victor Costan wrote:
> On Wed, Dec 5, 2012 at 12:11 PM, Ian Hickson wrote:
> > On Wed, 5 Dec 2012, Victor Costan wrote:
> >>
> >> There was a thread on this mailing list discussing making it possible
> >> to set the file data behind an element.
> >> http://lists.whatwg.org/h
On Thu, 17 Jan 2013, Jonathan Watt wrote:
>
> The text on at:
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#range-state-%28type=range%29
>
> says:
>
> The step scale factor is 1. The default step is 1 (allowing only
> integers, unless the
On Thu, 17 Jan 2013, Jonathan Watt wrote:
>
> I'm working on implementing for Gecko and have
> encountered what I believe to be an issue in the spec.
>
> Step 1 of the algorithm to find the "step base":
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attribu
The text on at:
http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#range-state-%28type=range%29
says:
The step scale factor is 1. The default step is 1 (allowing only
integers, unless the min attribute has a non-integer value).
I found the words
On 17/01/2013 19:29, Jonathan Watt wrote:
I'm working on implementing for Gecko and have encountered
what I believe to be an issue in the spec.
Step 1 of the algorithm to find the "step base":
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#conc
I'm working on implementing for Gecko and have encountered
what I believe to be an issue in the spec.
Step 1 of the algorithm to find the "step base":
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#concept-input-min-zero
says "If the element h
On Thu, 17 Jan 2013, Steve Faulkner wrote:
> hixie wrote:
> > > On Sun, 10 Jun 2012, Steve Faulkner wrote:
> > > >> >
> > > >> > You don't clearly differentiate between roles, properties and
> > > >> > states, ther are quite a few states and properties NOT provided
> > > >> > in HTML5 that may ha
On Thu, 17 Jan 2013, David Carlisle wrote:
>
> By adding
>
> "-//W3C//ENTITIES HTML MathML Set//EN//XML"
>
> To the list in
>
> 13.2 Parsing XHTML documents
>
> Of Identifiers that are recognised when parsing XHTML syntax documents.
What problem does this solve?
> The current list gives no
hixie wrote:
> > On Sun, 10 Jun 2012, Steve Faulkner wrote:
> > >> >
> > >> > You don't clearly differentiate between roles, properties and
> > >> > states, ther are quite a few states and properties NOT provided in
> > >> > HTML5 that may have use cases for adding to an input element, for
> > >>
This is a further attempt to resolve the bug report (currently with
status wontfix) regarding XHTML entity definitions.
(whatwg)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17798
(w3c)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13409
By adding
"-//W3C//ENTITIES HTML MathML Set//EN//X
It appears that WebIDL-ese has afflicted DOMError and DOMException:
http://dom.spec.whatwg.org/#interface-domerror
These should be constructable, with a single "name" DOMStrong parameter or
an argument bag which allows setting of the name property.
Regards
17 matches
Mail list logo
