Am Mittwoch, den 03.06.2009, 13:23 +0200 schrieb Kristof Zelechovski:
The validator generates an error for the classid attribute (in line with
what the specification says, I think). An error, unlike a warning, breaks
any complex process that depends on successful validation of the components.
The ActiveX components I use are proprietary non-standard technology.
Granted. However, the interface to them, HTML, is standard and
non-proprietary. Of course, one can use proprietary extensions like
namespaces and data sources as well, and sometimes it is necessary for
rendering and data
On Sun, 5 Apr 2009, Giovanni Campagna wrote:
A few comments, as requested by Ian Hickson.
- End of 2.2.1, a typo: JavsScript instead of Javascript
Fixed.
- From section 2.4.2 I don't understand if boolean attributes with
invalid values represent true or false. In addition, I don't
On Sun, 5 Apr 2009, Kristof Zelechovski wrote:
Now that classid is gone, what will be the workaround for ActiveX
objects where they are needed?
ActiveX controls are a vendor-specific technology, and thus not
appropriate for explicit support in HTML5 (just like we dropped applet).
The real
On Sun, 5 Apr 2009, João Eiras wrote:
The spec does not forbid to use non supported attributes and elements.
Actually, it does. I've just made the spec even clearer about this,
though.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/
On Sun, 5 Apr 2009, Christoph Päper wrote:
Giovanni Campagna:
- The second paragraph in 2.4.5.6 is hard to understand because the
verb is at the end. I would rewrite as
A week-year with a number *yr* has 53 weeks if corresponds to a year *yr*
in the proleptic Gregorian calendar that has a
The validator generates an error for the classid attribute (in line with
what the specification says, I think). An error, unlike a warning, breaks
any complex process that depends on successful validation of the components.
I think the specification text should be rephrased so that the validator
Regarding
http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.
html#weeks:
A week begins on Sunday, not on Monday.
However, under the present assumption:
Better:
A week-year has 53 weeks if the first day of the year (January 1st)
in the proleptic Gregorian calendar
Kristof Zelechovski wrote:
Regarding
http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.
html#weeks:
A week begins on Sunday, not on Monday.
Not according to ISO [1]
[1] http://en.wikipedia.org/wiki/ISO_week_date
On Sun, Apr 5, 2009 at 9:04 AM, Giovanni Campagna
scampa.giova...@gmail.com wrote:
A few comments, as requested by Ian Hickson.
[...]
- In section 3.3.3.7, instead of defining the syntax of style
attributes, reference http://www.w3.org/TR/css-style-attr
The style property has been part of
It is possible to create no-script fallback without a NOSCRIPT element. You
can put it into d...@class=noscript] and remove the DIV at run time.
It is worth noting that XHTML 1.0, along with deprecating MAP/@name, still
has the unrealistic assumption about usemap containing an arbitrary URI. I
A few comments, as requested by Ian Hickson.
- End of 2.2.1, a typo: JavsScript instead of Javascript
- From section 2.4.2 I don't understand if boolean attributes with
invalid values represent true or false. In addition, I don't
understand if an empty value is false (as in XHTML1.0) or true (as
Character set x-x-big5 cannot be registered because it is private.
Now that classid is gone, what will be the workaround for ActiveX objects
where they are needed?
1. Ask Windows browsers to support
Type=application/x-oleobject;classid=...?
2. Use a custom DTD with classid for
On , Kristof Zelechovski giecr...@stegny.2a.pl wrote:
Character set x-x-big5 cannot be registered because it is private.
Now that classid is gone, what will be the workaround for ActiveX objects
where they are needed?
classid is nevertheless proprietary, and no other user agent but IE will
The specification forbids the authors using undefined elements and
attributes; a document containing classid will not be valid. Still, the
site hosting the controls will need a way to test validity of pages for QA.
Chris
Giovanni Campagna:
- The second paragraph in 2.4.5.6 is hard to understand because the
verb is at the end. I would rewrite as
A week-year with a number *yr* has 53 weeks if corresponds to a
year *yr* in the proleptic Gregorian calendar that has a Thursday
as its first day (January 1st), or
16 matches
Mail list logo
