Re: [whatwg] Make quoted attributes a conformance criteria
> I'd say it is safe to say that using quotation marks for attribute values, > always, except perhaps for collapsed, boolean attributes, has been regarded > as best practice for a long time now. This always rather seemed like a preference to me, one that gets supported by consistency considerations (as some values would require quotation marks). Not considering the unquoted attribute value syntax a problem I’d second consistent use in the spec but would object any further changes. (I know first-hand that omitting optional tags alone gives people the creeps, but both optional tags and unquoted attribute values are valid options for writing HTML.) Couldn’t but add these two cents, Jens. -- Jens Meiert http://meiert.com/en/
Re: [whatwg] [html5] Semantic elements and spec complexity
On Tue, Feb 10, 2009 at 10:02 AM, Ian Hickson wrote: > On Thu, 11 Nov 2004, Matthew Thomas wrote: > > On Wed, 10 Nov 2004, James Graham wrote: Brilliant. I'm opting out of replies to my 2004 mails though ;) -- Jens Meiert http://meiert.com/en/
Re: [whatwg] Proposal: target="_tab"
> > What is interesting though is that authors can let open new windows/tabs > > by HTML, CSS, /and/ scripting. I am not sure if this functionality, that > > may ultimately impede user experience, can really be considered > > structural, presentational, /and/ behavioral. > > I have no idea what you mean or how it affects the spec. And you don't have to as it was just a side note. HTML 5 won't resolve this anyway. -- Jens Meiert http://meiert.com/en/
Re: [whatwg] Proposal: target="_tab"
> > In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that > > authors should have the ability to suggest that links open in new > > windows and new tabs. The suggested solution is to introduce a new > > browsing context keyword "_tab". > > In general, it's best to let users decide where the link should open. Absolutely agreed. What is interesting though is that authors can let open new windows/tabs by HTML, CSS, /and/ scripting. I am not sure if this functionality, that may ultimately impede user experience, can really be considered structural, presentational, /and/ behavioral. -- Jens Meiert http://meiert.com/en/
Re: [whatwg] Proposal: target="_tab"
> In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that authors > should have the ability to suggest that links open in new windows and new > tabs. The suggested solution is to introduce a new browsing context keyword > "_tab". Wondering: How is CSS 3's Hyperlink Presentation Module [1] (and its "target-new" property) supposed to fit in, /theoretically/ allowing us to drop @target altogether? [1] http://www.w3.org/TR/css3-hyperlinks/ -- Jens Meiert http://meiert.com/en/
[whatwg] Spec review results I
Since currently reviewing and proof-reading the HTML 5 spec draft
(again) I'm feeling free to send (rather non-technical) /suggestions/
and eventual typos to this list. This tiny first part refers to CVS
revision 1.904 [1].
* Please drop "or the idea that the working group should even spend
time discussing the concept of that section" as this is unnecessarily
judgmental.
* Change order of change history locations [2] (inverting the order
seems to make sense to put more emphasis on CVS/SVN access than on
Twitter).
* Remove emphasis from "This" in "This specification aims to extend
HTML so that it is also suitable in these contexts" [3] (and probably
use "The HTML 5 specification" instead of "This") as this
unnecessarily seems to judge XHTML 2.
* Better write "HTML documents do not exist in a vacuum. This section
…" instead of "HTML documents do not exist in a vacuum — this section
…" [4].
* In the same section [4] it might be fine to drop the first half of
the Language Syntax description, "All of these features would be for
naught if they couldn't be represented in a serialized form and sent
to other people, and so …".
* Add a period behind "etc" (many occurrences), as I Merriam-Webster
[5] and Wikipedia [6] seem to confirm ("Typically, the abbreviated
versions should always be followed by a full stop").
* In the conformance section [7], "if errors have been so preserved"
might be rephrased to "if errror have been preserved this way" or the
like (not too sure about it, but the current phrase sounded strange to
my non-native ears).
* Please simplify the "Unless otherwise specified …" exception notes
[8] as there is a lot of redundancy.
[1] http://dev.w3.org/cvsweb/~checkout~/html5/spec/Overview.html?rev=1.904
[2]
http://dev.w3.org/cvsweb/~checkout~/html5/spec/Overview.html?rev=1.904#status
[3]
http://dev.w3.org/cvsweb/~checkout~/html5/spec/Overview.html?rev=1.904#relationship0
[4]
http://dev.w3.org/cvsweb/~checkout~/html5/spec/Overview.html?rev=1.904#structure
[5] http://www.merriam-webster.com/dictionary/etc
[6] http://en.wikipedia.org/wiki/Et_cetera
[7]
http://dev.w3.org/cvsweb/~checkout~/html5/spec/Overview.html?rev=1.904#conformance
[8]
http://dev.w3.org/cvsweb/~checkout~/html5/spec/Overview.html?rev=1.904#common
--
Jens Meiert
http://meiert.com/en/
Re: [whatwg] Feeedback on , , and other elements related to cross-references
> The point of is to expand the acronym, not to just mark up what is > an acryonym or abbreviation. Doesn't this claim that the general information that some text is an abbreviation (w/o an expanded form) is basically useless? And is "ISS" not more useful since less ambiguous than "ISS" (same abbreviation) and "ISS" (German imperative for "to eat" in capitals), and be it just for AT, pronunciation and a scent of semantics? And why do we need to change what HTML 4 left "open" anyway in the first place; I'm still not convinced that "indicates" really /needs/ to be replaced by "expands": ABBR: Indicates an abbreviated form (e.g., WWW, HTTP, URI, Mass., etc.). [1] [1] http://www.w3.org/TR/html4/struct/text.html#edef-ABBR -- Jens Meiert http://meiert.com/en/
Re: [whatwg] Web Forms 2.0 is now a W3C Working Draft
Slightly off-topic - what I like most is this ultra-sensitive and tactful "for example the activation code for a nuclear weapon" [1] Impressive. [1] http://www.w3.org/TR/web-forms-2/#the-autocomplete -- Jens Meiert http://meiert.com/ Webdesign mit CSS (O'Reilly, German) http://meiert.com/cssdesign/
