reason for dropping it.)
> (A streaming browser will may hit this case after parsing the first
> radio button element in the document. Then what?)
Then browsers will follow the parsing algorithms and treat it
accordingly. For backwards compatibility and interoperability, the spec
covers how to
ing to add or change any existing theme-color.
It's also much easier to teach ‘if you want a red house, draw a solid
house in the particular share of red you want’ than ‘if you want a red
house, draw it in solid black, then specify the shade of red separately
in multiple files that yo
ady is a solid
shape of the correct colour (so it can be used as a colour icon, too),
why should they have to specify that colour a second time in their HTML?
You already know what the colour is, from the icon itself.
Smylers
--
http://twitter.com/Smylers2
l links to them.
> Alternatively, wrap the element in a div with a new id.
Or have some JavaScript which checks for known alternative anchors and
replaces them with their canonical spelling.
Smylers
--
http://twitter.com/Smylers2
ng ‘undo’ unsets the ‘dirty’ flag.
(Note I'm not arguing that the feature is, on balance, worth including,
merely answering the questions you asked.)
Smylers
--
http://twitter.com/Smylers2
in a photo album and
> > would like to make sure these images are lower priority than images
> > the user is actually viewing.
>
>
>
>
>
>
>
> As they come into view, they'll become needed automatically. When they
> are not needed, they get precached if that wouldn't get in the way of
> other things getting loaded.
Thanks.
Smylers
--
http://twitter.com/Smylers2
Ryosuke Niwa writes:
> On Mar 11, 2014, at 2:28 AM, Smylers wrote:
> >
> > Ryosuke Niwa writes:
> >
> > > On Mar 7, 2014, at 3:54 AM, Smylers wrote:
> > >
> > > > Are there many websites currently catering [for] Japanese years
> > >
Ryosuke Niwa writes:
> On Mar 7, 2014, at 3:54 AM, Smylers wrote:
>
> > An international website wanting a [year] ... could internally store
> > all years using one particular system (say the Gregorian one), but
> > allow input in other systems. This could be with a fre
ith the term; I can't find it in the ‘Oxford
English Dictionary’), but if it's appearance, interface, and behaviour
are identical to that of , what is the point of
distinguishing the two?
Cheers
Smylers
--
http://twitter.com/Smylers2
Ryosuke Niwa writes [re-ordered]:
> > On Feb 19, 2014, at 7:36 AM, "Jukka K. Korpela"
> > wrote:
> >
> > 2014-02-19 11:10, Smylers wrote:
> >
> > > Jukka K. Korpela writes:
> > >
> > > > The point is that year numbers aren
Jukka K. Korpela writes:
> 2014-02-19 11:10, Smylers wrote:
>
> > Jukka K. Korpela writes:
> >
> > > The point is that year numbers aren't really "numbers" in a normal
> > > sense, any more than car plate numbers, credit card numbers,
&g
[*1] Yes, there are exceptions. But there are still many situations
where this is useful, because of the context, such as the range of
possible years and the location.
Smylers
--
http://twitter.com/Smylers2
continuing to grow at a massive rate, so they are likely to
be far more web developers in the future than there have been developers
so far. In other words, most developers using this API won't have
existing experience of pre- systems' dash-drawing APIs — and
that will become more so as tim
d for any
further label.
Or the content of a figure may intrinsically have a title embedded in it
already, such that an additional caption would be superfluous.
Smylers
--
Stop drug companies hiding negative research results.
Sign the AllTrials petition to get all clinical research results pub
Robin Berjon writes:
> On 04/06/2013 11:08 , Smylers wrote:
>
> > Michael[tm] Smith writes:
>
> > > we receive a lot of comments and bug reports from confused/
> > > frustrated users who are trying to use values for meta@name that
> > > are not registe
please tell me its purpose here, then I'll know what it's for
and I won't complain about it again: __
Then the validator could add a wiki entry for it.
Cheers
Smylers
--
Stop drug companies hiding negative research results.
Sign the AllTrials petit
e promoter of the feature,
can't even get it right suggests that it would also be hard for authors
to do so.
Cheers
Smylers
--
New series of TV puzzle show 'Only Connect' (some questions by me)
Mondays at 20:30 on BBC4, or iPlayer: http://www.bbc.co.uk/onlyconnect
hat
generator.
If the validator can do something different which wouldn't nudge
developers into writing software which produces such mark-up, end-users
benefit.
Smylers
--
http://twitter.com/Smylers2
tant value for 'delivery address', but would
like both of them remembering and to be available.
> and optionally offer to set the control to that value.
Or optionally just set the control to the value, without offering, like
password managers typically do? Or is that too risky, because a site
could have JavaScript which automatically submits a form after a short
delay, to see if the browser has filled in any details for the user?
But maybe an option for 'and automatically do this in future for this
site' would be OK?
Cheers
Smylers
--
http://twitter.com/Smylers2
Aryeh Gregor writes:
> On Thu, Jul 26, 2012 at 11:52 AM, Smylers wrote:
>
> > Perhaps specifying certain autocomplete types could set defaults for
> > pattern and inputmode? So for this example autocomplete=cc-num
> > would, if pattern isn't specified, imply pattern
ving the highly foreseeable cases merely be defaults for pattern
and inputmode, it allows anybody doing something less predictable to
still set those attributes explicitly.
The complicated cases would be possible, but wouldn't force redundancy
on the common cases.
Cheers
Smylers
--
http://twitter.com/Smylers2
ypes of ID
numbers contain letters as well.
OpenID URLs could be viewed as one example of cross-site membership, so
could possibly be covered by a system such as this. But since OpenID is
an open standard which anybody can use, and isn't tied into a particular
organization, an autocomplete type specifically for OpenID URLs may be
worthwhile.
Cheers
Smylers
--
http://twitter.com/Smylers2
of an
> (header-article-footer), it is already an habit to see the [author]
> data in both locations ( and ).
Indeed.
> the question will became a simple matter of taste and habit.
It already is, with the spec as it is.
Smylers
--
http://twitter.com/Smylers2
All "web+" schemes should use UTF-8 encodings were relevant.
--
http://www.whatwg.org/specs/web-apps/current-work/multipage/iana.html#web+-scheme-prefix
I think that should be "where".
Smylers
--
http://twitter.com/Smylers2
too -- in particular
authors wondering if they can extend HTML.
Currently 'HTML5 for Web Developers' has a link 'other applicable
specifications' which doesn't go anywhere:
http://developers.whatwg.org/elements.html
Cheers
Smylers
around
> > the turn of the millennium.
> >
>
> ... the current markup handles it fine already (as you demonstrate
> above).
Using like that isn't conforming, surely?
Smylers
Ian Hickson writes:
> On Sat, 7 Jan 2012, Smylers wrote:
>
> > > If it's something you'd find useful even in its incomplete state,
> > > I can add an alternative style sheet
> >
> > Yes, please.
>
> Roger. I've added an alternative sty
Ian Hickson writes:
> On Thu, 29 Dec 2011, Smylers wrote:
>
> > Hi there. Is there still a version of the HTML5 spec with
> > implementation-only parts highlighted?
>
> The annotations in the spec were incomplete -- they only covered the
> parts of the spec th
'implementors' part of the question no longer answered:
http://wiki.whatwg.org/index.php?title=FAQ&diff=7213&oldid=7212
Thanks
Smylers
--
http://twitter.com/Smylers2
ut it at least means that going forwards authors could opt
in to the sane behaviour. And any author who complains about the
-s not being quite as they wanted could be pointed at the pre-wrap
alternative.
Smylers
--
http://twitter.com/Smylers2
perhaps a slightly bigger change than you
intended to introduce.
Smylers
--
http://twitter.com/Smylers2
er, a public computer, . . .).
Even so, that still doesn't help. You _also_ have to know whether the
author just wrote the date in text or used the element, in order
to know whether your browser has already localized the date for you.
Which, in general, an author will have no way of knowing.
Smylers
--
http://twitter.com/Smylers2
une/000561.html
Please could this be added to the 'idioms' section, perhaps giving
examples of when or might be appropriate as well as
one in which the main content is simply that which isn't in ,
, etc.
Thanks.
Smylers
--
http://twitter.com/Smylers2
has to wait for server-side validation.
Smylers
gt; content isn't actually filling an entire screen,
Allowing that behaviour is entirely reasonable. Though I think it
should be covered by a more general statement that user-agents may
display things however they want if so-configured, rather than just
stating it for this particular nar
splay some content full-screen, so grants
permission and views it.
3 A user doesn't wish to display some content full-screen, so ignores
any attempt by the site to become full-screen, and continues to view
it normal size.
I'm struggling to come up with a scenario in which
on to refer to well-known works by nicknames, such as 'Smith &
Thomas', 'The Dragon Book', 'The Red Book', or 'The White Album'. So
should be used for them.
But it doesn't follow that should be used for any other
occurrences of those terms -- the people Smith and Thomas, or a book
which just happens to be red.
Smylers
doing something of no benefit.
> These do seem useful; if you wanted more information, it might well be
> "How do I contact this photographer or that model to get something
> similar?"
How does the use of make that any easier for users than if, say,
(or or or whatever) had been used instead?
Smylers
n the current context, rather than denoting them as
being important?
Smylers
the HTML5 specification?
Doing the above never made sense, notwithstanding and interpretations of
HTML4 which suggest otherwise.
> And as Jeremy Keith and others have pointed out, there's nothing wrong
> with overriding default presentational styles. I'm not sure why it
> should be such a cause for concern with .
Overriding is very differnt from trying to remove the effects of.
> I believe I understand why you have chosen to define as it
> appears in the current draft of the HTML5 specification; I just happen
> to believe that the current definition is not as useful as it could be
> and (more importantly) invalidates current reasonable uses of the
> element.
Why is that important?
Automated validators generally won't catch it, so it won't make previous
valid pages suddenly spew dozens of errors (a concern with other changes
from HTML4).
And if authors of such pages on discovering non-title uses of
aren't valid then remove them, that's a win for users of non-CSS
browsers.
Smylers
no" for is class=impl but the equivalent one
for isn't.
While proofreading this change I also spotted an inconsistency in the
related example undet the element:
http://www.whatwg.org/html5#the-dd-element
I think the first class=part-of-speech should be on the rather than
the (matching the other instances).
Smylers
of HTML 5:
standardizing previous stupidities so that we can all share in them.
(We've already tried the alternative, and it's worse.)
Smylers
is what's holding them back.
> I really don't see a case for not allowing pattern for a textarea.
The point is to have cases specifically _for_ it -- not adding
everything for which there isn't a reason against.
If wouldn't in practice be used by authors then
there's no point in adding it. If it would be used then it should be
trivial to show some places where it would be used.
Smylers
Aryeh Gregor writes:
> On Mon, Aug 24, 2009 at 4:36 AM, Smylers wrote:
>
> > It's too complicated for most developers to roll their own
> > validation, but there are standard libraries available which get it
> > right.
>
> Standard libraries available for all
Aryeh Gregor writes:
> Historically, MediaWiki has mostly just required that an @ symbol be
> present in the address. Originally we used a simplistic regex,
It's relatively well known that a simple regex can't be used to match
e-mail addresses (and not match things that aren't!); Jeffrey Friedl'
s a competition on
it (in regular sized text) followed by:
Terms and conditions apply. For full details see the
http://www.bbc.co.uk/terms/";>standard BBC T&Cs..
In that case the short amount of 'small print' is distinguished from the
surrounding text. Visual users can see it as such; a speaking browser
could read it out faster.
Smylers
Erik Vorhes writes:
> On Thu, Aug 13, 2009 at 4:59 AM, Smylers wrote:
>
> > For words that you wish to have no distinct presentation from the
> > surrounding text -- words that readers don't need calling out to
> > them as being in any way 'special' -- simp
ion in the survey.
Typically these are static to the page (as in, making progress and
seeing the indicator move involves submitting a form and displaying the
next page in the sequence), but so far as I can see from the spec
can be used in these situations; it isn't restricted to use
on a single page where it is updated dynamically.
Smylers
Erik Vorhes writes:
> On Thu, Aug 13, 2009 at 4:59 AM, Smylers wrote:
>
> > As Ian has pointed out, the above is technically non-conforming with
> > what the HTML 4 spec claims. But it's how I've been using for
> > years, since it makes sense and has a use.
n; and its default display in existing browsers is the
common typographic style for the useful definition (which gives weight
to the idea that the HTML 5 definition is actually what at least some
people intended in the first place, or have already been using it as).
So tweaking the definition to be more useful seems better than inventing
a new element with a better name.
Smylers
Ian Hickson writes:
> On Thu, 6 Aug 2009, Smylers wrote:
>
> > Instead of setting the smaller font on the boxes, set it on all
> > their children (.box > * -- or whatever the class name is). This
> > still makes the text smaller. But that leaves the width of
e same as the margin it needs to
fit in. As such it's trivial to pick a size that always fits.
I hadn't yet submitted this because I first planned to try it in more
browsers. In particular I'm concerned that the child selector isn't
support in some IE versions.
Hope that helps.
Smylers
wha...@whatwg.org writes:
> + The Web Socket protocol is an independent TCP-based
> + protocol. It's only relationship to HTTP ...
An apostrofly has crept in there.
Smylers
Ian Hickson writes:
> On Fri, 19 Jun 2009, Smylers wrote:
>
> > For 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
&g
y send back to the server. But
surely a UA can pick any UI they want for this -- including a text box
where the user types a comma, and a decimal point displays as a comma?
Smylers
There's a run-on sentence:
The LinkStyle interface must also be implemented by this element, the
styling processing model defines how.
-- http://www.whatwg.org/html5#htmlstyleelement
(Changing the comma to a semicolon would fix it.)
Smylers
to establish if a value not explicitly defined
in this specification is allowed or not.
-- http://www.whatwg.org/html5#other-pragma-directives
Also, the above sentence isn't marked up as an implementation
requirement.
Smylers
rwise
unconstrained inputs, e.g. to prevent denial of service attacks, to
guard against running out of memory, or to work around
platform-specific limitations.
-- http://www.whatwg.org/html5#conformance-requirements
Smylers
transformation program outputs an element in no namespace,
> + the processor must ...
Should this text be marked up as an implementation requirement?
Smylers
l5#a-quick-introduction-to-html
"Generally will be" seems to be a prediction that the spec doesn't need
to make, and could be seen as a recommendation for authors to quote
attributes even when they're unnecessary.
Could we simply omit that (finishing the sentence at "keyword")?
Smylers
ing both HTML and XHTML is "encouraged",
user-agents "may" choose to support only one of them:
http://www.whatwg.org/html5#conformance-requirements
Smylers
ce it seems that sites which style ledes also have a
journalistic house style which requires journalists to consistently have
the lede be the first paragraph (or whatever).
Smylers
timeless writes:
> On Fri, Jun 19, 2009 at 2:32 PM, Smylers 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
vant sections -- for example the rules on when to use which of
, , or providing alt text for images.
Smylers
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.
Those things all seem much more obvious to me than working out which day
January 1st of a given year is. But as I said, I'm not a browser
developer so perhaps it's fine.
Smylers
Anne van Kesteren writes:
> On Fri, 19 Jun 2009 11:48:17 +0200, Smylers
> 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 suffici
of 'input', then fail.
That would appear to fail on "10:55". I think making step 10 begin "If
the 'date present' and 'time present' flags are both true" (as step 11
already does) fixes this.
Smylers
e have to
implement a 'which day is January 1st' algorithm, which I'm guessing it
currently doesn't).
Smylers
lo, and Lynx all also seem to manage the aborting, but use a default
of zero instead. Firefox parses the "2" out of "H2SO4", seemingly using
the first integer it can find in the attribute, so possibly isn't
special-casing "+".
Smylers
idate matters:
http://www.whatwg.org/html5#serializability-of-script-execution
What's this about?
Smylers
seems oddly
inconsistent. Could we have them matching?
(I haven't searched to see if this also occurs elsewhere in the
document.)
Smylers
uthor).
There may be parts which do require Dom knowledge, but as written it
sounds like a prereq for understanding any part of the spec, and as such
may unnecessarily put people off.
Smylers
't apply to
him, since he's never intended his tool to conform to it.
Could we make it something like "implementors of tools that emit HTML or
parse Web content"?
Smylers
, in that I don't think
it's currently possible with CSS. But that it exists as a plausible
choice for presenting an article demonstrates how much a matter of
styling, rather than content, this area is. And a limit of CSS should
be fixed in CSS, not HTML. ( can always be used as a
work-around.)
Smylers
ontent to follow (almost like legalese on radio
adverts). That suggests the element, but that isn't quite right
either: whether a section is normative is materially relevant to the
content, not just a legal technicality.)
Smylers
tent was manually added at the top; I'm not sure if it ever
disappeared from the bottom, until the entire blog was abandonned.
The 'subscribe' link is to get e-mail updates.
Smylers
t that's quite possibly because of the effort involved in
doing so. The algorithm in the HTML 5 spec would allow some categories
of handcrafted pages to gain feeds for free.
I've often encountered webpages which I wished had feeds but don't.
It's possible that an algorithm such as this would encourage more pages
to do so.
Smylers
Eduard Pascual writes:
> On Fri, May 15, 2009 at 8:40 AM, Smylers wrote:
>
> > > Am Freitag, den 08.05.2009, 19:57 + schrieb Ian Hickson:
> > >
> > > > * Tara runs a video sharing web site for people who want
> > > >licens
license" then she's likely to realize it's licencing information. And
if it's placed next to a picture it's conventional to interpret that as
applying to a picture. It's also conventional for such information to
be small, because it's usually not the main content the user is
interested in when choosing to view the page.
Magazines and the like have been using this convention for years,
without any need to explicitly define what indicates licensing
information, seemingly without any ambiguity or confusion.
Smylers
jgra...@opera.com writes:
> Quoting Smylers :
>
> > James Graham writes:
> >
> > > affects the document structure, does not.
> >
> > That explains _how_ they are different (as does the spec), but not
> > _why_ it is like that.
> >
> >
(but only acted as a heading if
there actually is an somewhere inside it) and if all current uses
of could be put inside a then we could avoid
introducing the element.
Smylers
[*1] is less likely to suffer from this since it's often
replacing or similar; authors want a block at that
point in the page anyway.
line-breaks
into tags and use of a monospaced typeface into spans, and
the two happened to co-incide -- possibly the robot's author never even
considered it.
Smylers
lized
version goes in the tooltip but the user sees exactly what the author
typed?
That is, which version (author-written or localized) the browser shows
in the page depends on which format the author used?
Smylers
://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#parse-a-date-component
Smylers
Andy Mabbett writes:
> In message <20090314083450.ga30...@stripey.com>, Smylers
> writes
>
> > This thread appears to be proving that dates are very complicated
> > and that to get them right for the general case involves lots of
> > subtleties,
>
> All t
k/multipage/infrastructure.html#parse-a-month-component
So my suggestion for a spec change is to replace "zero" with "1582".
That further reduces the set of dates that can represent, but
avoids the complexity of pre-Gregorian dates, and avoids inadvertently
giving a meaning to them that hampers the efforts of a future version of
HTML to do all of this right.
Smylers
e/infrastructure.html#valid-date-string
Which must start with a valid month string:
http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#valid-month-string
Which has the constraint year > 0.
Smylers
Aryeh Gregor writes:
> On Wed, Feb 11, 2009 at 10:13 AM, Smylers wrote:
>
> > Ah, I see. Thanks for explaining that. I'm interpreting it as "for
> > each bit of text that you cause the background colour to be set for,
> > also specify its foreground colour (a
Aryeh Gregor writes:
> On Wed, Feb 11, 2009 at 8:36 AM, Smylers wrote:
>
> > That is precisely an instance of an author setting a background
> > colour without a foreground colour -- specifically the author set
> > the background colour used on links without setting t
king your -s green will assist me
in doing that.
> I don't think there's any way around this.
We don't want a way "round" it. It's a feature that users are in
ultimate control.
Smylers
the difference between a normal
> hyphen and a soft hyphen then...)
Suppose you are reflowing some text (perhaps because you are quoting
it); words which were broken over lines in the original may want
rejoining into a single word in your version (that is, the soft hyphen
disappears); but hyphens (non-soft) between two words need to remain.
Smylers
ng for
> those author that didn't follow rule 1), I import HTML5 style sheet
> inside UA defaults. In both case, a downloadable stylesheet would be
> much appreciated.
I think a downloadable style-sheet is inevitable!
Smylers
Giovanni Campagna writes:
> 2009/2/8 Smylers
>
> > Giovanni Campagna writes:
> >
> > > data:text/html,label { position:fixed; top:-1em; border:1px
> > > solid black; } label input { -moz-appearance:none;
> > > -webkit-appearance:none; border:none;
aying certainly elements which she considers is superior for
her particular target audience; why should the spec attempt to dissuade
her from doing so?
Smylers
Authenticate: HTML form="login"
That is, the HTTP header specifies the name of which form to use.
Smylers
checks legacy content against the new
standard they will discover that what they did is no longer recommended.
However, browsers will 100% support it and continue to render it as it
always has been, so the 'breakage' is no way visible; if the author
chooses not to care about it then no harm is
Felix Miata writes:
> On 2008/11/24 16:19 (GMT) Smylers composed:
>
> > So I still think works for denoting that something is of
> > smaller importance.
>
> I do too, but I don't believe less importance can be the only
> inference. One could simply want smal
Asbjørn Ulsberg writes:
> On Mon, 17 Nov 2008 15:26:22 +0100, Smylers <[EMAIL PROTECTED]>
> wrote:
>
> > In printed material users are typically given no out-of-band
> > information about the semantics of the typesetting. However,
> > smaller things are le
ships that rel allows there are relationships
in each direction (both from and towards the current document), but a
given relationship is always unambiguously defined to be in a particular
direction.
> > If there are redundant features that are only used 0.2% of the time,
> > we should probably remove them, yes. Are there any?
>
> A lot considering that the average website only uses 19 elements[1]
That simply doesn't follow. There are many ways in which hundreds of
different elements could be distributed throughout a population such
that each of them are used on more than 0.2% of pages yet the mean
elements per page is 19.
Smylers
te; given rel's existence, the cost of
adding start, up, etc is quite possibly less than of adding rev.
There's also the misuse to consider. If, say, rel=up is barely used but
when it is used it's generally used correctly then it's benign, and not
causing any harm. Significant rev misuse has been identified; its
existence is confusing people into writing something they don't mean.
Smylers
1 - 100 of 142 matches
Mail list logo
