For input type=week elements the spec requires:
The value attribute, if specified, must have a value that is a valid
week string.
-- http://www.whatwg.org/html5#week-state
But the spec's HTML source contains this comment immediately afterwards:
!-- ok to set out-of-range value, we
On Fri, 19 Jun 2009 11:48:17 +0200, Smylers smyl...@stripey.com wrote:
The spec doesn't appear to provide an algorithm for determining which
day of the week a year begins on (however I am not a browser developer;
possibly this is sufficiently straightforward that those who are don't
need it
Anne van Kesteren writes:
On Fri, 19 Jun 2009 11:48:17 +0200, Smylers smyl...@stripey.com
wrote:
The spec doesn't appear to provide an algorithm for determining
which day of the week a year begins on (however I am not a browser
developer; possibly this is sufficiently straightforward
An algorithm for calculating the weekday of Jan. 1st given a year would be
outside the scope of the HTML specification. Similarly, the HTML
specification does not describe how you increment a number by 1.
IMHO,
Chris
You can easily include a cross-domain script using a cross-domain DTD; just
attach the malware as
!ATTLIST body onload CDATA { sniper.shoot(); }
and hope for the worst.
Chris
Unlike in previous versions, the DOM is the skeleton and the underlying
model of the specification. Even if there are sections that do not
reference the DOM explicitly, a reader that tries to apply them to anything
will not probably be able to draw the right conclusions without a basic
knowledge
A lede is a summary or an invitation to read the whole article.
It is semantically relevant; the reader may ask, e.g., Give me the ledes
and I shall choose what I would like to read. Asking for the first
paragraph of each article is not that practical, as the article need not
contain a lede
Křištof Želechovski writes:
An algorithm for calculating the weekday of Jan. 1st given a year
would be outside the scope of the HTML specification.
That's begging the question.
Similarly, the HTML specification does not describe how you increment
a number by 1.
No, but it does explain how
On Fri, Jun 19, 2009 at 2:32 PM, Smylerssmyl...@stripey.com wrote:
The 'week number of the last day' of a week-year with 53 weeks is 53;
the 'week number of the last day' of a week-year with 52 weeks is 52.
well... there are people who might think you could count from week 0
if weeks are
An algorithm to calculate the weekday of Jan. 1th given a year is not
obvious at all. Just the opposite: the more obvious an external fact is,
the easier (and more appropriate) it is to incorporate it to the
specification because it does not cause any distraction from the main
subject.
Cheers,
2009/6/19 Kristof Zelechovski giecr...@stegny.2a.pl:
You can easily include a cross-domain script using a cross-domain DTD; just
attach the malware as
!ATTLIST body onload CDATA “{ sniper.shoot(); }”
and hope for the worst.
Chris
You need to own the external subset, though, in order to
Kristof Zelechovski writes:
Unlike in previous versions, the DOM is the skeleton and the
underlying model of the specification.
Yup. But I don't think any more Dom knowledge is needed to read this
version.
Even if there are sections that do not reference the DOM explicitly, a
reader that
timeless writes:
On Fri, Jun 19, 2009 at 2:32 PM, Smylerssmyl...@stripey.com wrote:
The 'week number of the last day' of a week-year with 53 weeks is 53;
the 'week number of the last day' of a week-year with 52 weeks is 52.
well... there are people who might think you could count from
Kristof Zelechovski writes:
A lede is a summary or an invitation to read the whole article. It is
semantically relevant; the reader may ask, e.g., Give me the ledes
and I shall choose what I would like to read.
For a user-agent to reliably provide that functionality would require a
specific
Getting the day of the week, in the Gregorian calendar, for a given date is
pretty straightforward. I thought we publihsed it online somehwere on the
Royal Observatory website, but I can't find it. However, wikipedia has the
algorithm:
It sounds like there wasn't any discussion on this. I recently heard
talk of other potential Storage areas [2]. That would make this idea
even more appealing to me. Does this sound like something worth
adding? Any comments?
[2]:
16 matches
Mail list logo
