Re: [whatwg] HTML tags for POEM and MUSIC LYRICS

> "Tab Atkins Jr." : > On Sun, Nov 26, 2017 at 8:59 AM, GevCbmlGM wrote: > > > > Is there any recommend standard HTML tags for POEM and MUSIC LYRICS? > > Poems and lyrics are, generally, just text that has significant > line-breaks. Thus, and are

[whatwg] Moving PNG Extensions to WhatWG

lists APNG as a possible specification to take under WhatWG wings. It currently lives dormant at . What would be needed to get this and other extensions to PNG that have not or will not get the okay from

Re: [whatwg] Typed numeric 'input'

Jukka K. Korpela jkorp...@cs.tut.fi: 2014-08-04 20:06, Christoph Päper wrote: Imagine a text layout GUI made with HTML. It would probably feature a font size selection control. There are different ways to do such a thing: There are, and they are preferred in different ways by different

[whatwg] Typed numeric 'input'

Imagine a text layout GUI made with HTML. It would probably feature a font size selection control. There are different ways to do such a thing: 1 input type=number min=0 id=value!--unit implied-- 2 input type=text id=value pattern=\d+([.,]\d+)? *(pts?|px|mm)\.? 3 input type=number min=0

Re: [whatwg] Sortable Tables

Ian Hickson: On Thu, 1 Jul 2010, Christoph Päper wrote: Darn, my reply from yesterday got lost in data nirvana. This is a slightly shorter version thereof. So sortable tables should be marked as such. Opt-in: table sortable collapsible “sortable=auto” should be the default and resolve

Re: [whatwg] Sortable Tables

Ian Hickson (2012-11-06): On Thu, 1 Jul 2010, Christoph Päper wrote: For starters, only rows inside ‘tbody’s shall be reordered. That means every row groupp shall be sorted independently from others, while ‘thead’ and ‘tfoot’ remain unsorted, possibly bearing sort widgets. Not every table

Re: [whatwg] Geographic hyperlinks

Bjoern Hoehrmann: * Christoph Päper wrote: geo:13.4125,103.8667@mars You can specify the coordinate reference system with the crs paramameter Yes, but I don’t think it’s a good design to select the astronomic body with the same property that you use to switch between different CRSs

Re: [whatwg] [Selectors4] case-insensitive attribute value matching (in XML)

Anne van Kesteren: I'm still trying to get HTML and browsers to change so that attribute values always match case-sensitively, irrespective of markup language. The current magic attribute list in HTML whose values needs to be matched ASCII case-insensitively is just ugly. Can’t that be

Re: [whatwg] Physical quantities: var or i?

Jukka K. Korpela: varc/var would be odd, wouldn't it, since the symbol denotes a universal constant of nature. It would not, ‘c’ is merely a variable with constant value. varE/var = varm/var·varc/varsup2/sup Or math, eventually.

Re: [whatwg] Why is @scoped required for style as flow content?

Jukka K. Korpela: Yet another reason for dropping style scoped in favor of an attribute referring to an external stylesheet. I’m not sure which of these I would hate the least: blockquote stylesheet=external.css… blockquote style=@import external.css;… blockquotestyle scoped

Re: [whatwg] Form input element for value-unit pairs

Markus Ernst: Am 15.03.2011 17:36 schrieb Christoph Päper: input name=fontsize type=number unit=typo datalist id=typo option value=2.835 label=pt option value=1 label=mm /datalist What I do not yet understand is, in what point does this proposal enhance usability compared

Re: [whatwg] Interpretation issue: can section be used for extended

Jacob Kristensen: Where you would typically see one large paragraph of text in books (to save space), you would see the same paragraph breaken up into multiple paragraphs on a web page, for readability purposes.. HTML isn’t used for Web pages only these days.

Re: [whatwg] Form input element for value-unit pairs

Jukka K. Korpela: Christoph Päper wrote: input type=number id=fontsize value=12 unit=pt Or do you mean that the presence of the unit=... attribute would trigger a special implementation of numeric input, so that the user is expected to enter both a number and a unit, with the latter

Re: [whatwg] Form input element for value-unit pairs

Christoph Päper (2011-03-05): Thus, would it make sense to add another new type for the ‘input’ element? A new type is probably not necessary, because a new attribute that is called something like ‘unit’ and is only valid in the ‘number’ and ‘range’ states could be enough. input type

Re: [whatwg] datalist @exclusive

Diogo Resende: I was thinking.. what about allowing big time spans, like: from April 1st to June 30th? Giving that the date has - as date element separators we could not use 1-MM1-DD1-2-MM2-DD2. ISO 8601 specifies how to code time intervals (and durations) in several ways: start

Re: [whatwg] datalist @exclusive

Jukka K. Korpela: Christoph Päper wrote: Diogo Resende: I was thinking.. what about allowing big time spans, ISO 8601 specifies how to code time intervals (and durations) … – the separator always is a forward slash ‘/’, replacable by a double hyphen ‘--’ if necessary. If HTML

[whatwg] Form input element for value-unit pairs

Imagine a richt text processor done in HTML5. If you want to select the font size (of a template or class, of course) how would you do it? Standalone word processors usually have a combo field that lets the user enter a number [12] possibly adding controls for increasng and decreasing

Re: [whatwg] Exposing spelling/grammar suggestions in contentEditable

Charles Pritchard: A method for a contentEditable section, along the lines of getSpellcheckRanges() would allow for content editors, to stylize and provide further UI controls around spell checking. Methinks this belongs into CSS:

Re: [whatwg] input type=number without keyboard editing

Aryeh Gregor: So if you wanted to change input type=number min=20 max=50 value=20 to 30, it would go like this: It would be more interesting with “value=40”. 1) Hit backspace, user sees 2, .value is 20, no input event fired 2) Hit backspace, user sees , .value is , input event possibly

Re: [whatwg] Please consider adding a couple more datetime input types - type=year and type=month-day

I’m not sure, but I think it’s at your end that character encodings get garbled. Ian Hickson: On Tue, 24 Aug 2010, Christoph Päper wrote: - Input two-digit year, transmit four-digit year. Do sites really want to support two-digit years? Not sites, year input widgets! - Input year name

Re: [whatwg] [br] element should not be a line break

Ian Hickson: On Wed, 4 Aug 2010, Thomas Koetter wrote: What strikes me though is that according to the spec The br element represents a line break. A *line* break is presentational in nature. The break is structural, but restricting it to a certain presentation of that break lacks the

Re: [whatwg] [html5] r4949 - [giow] (0) The CSS rules need to do attribute value matching consistently across [...]

Anne van Kesteren: On Wed, 25 Aug 2010 01:00:50 +0200, Ian Hickson i...@hixie.ch wrote: I'm sure people do: P ALIGN=CENTER ... /P Sure, but I highly doubt people do that and expect p[align=center] to work, especially since that has not always worked in all browsers. I for one

Re: [whatwg] Please consider adding a couple more datetime input types - type=year and type=month-day

Henri Sivonen: On Aug 9, 2010, at 04:07, Tantek Çelik wrote: * it has the *semantic* of being a year, Why is it useful to declare this semantic to the browser? What functional difference do you envision compared to a field that accepts an integer (…)? - Input two-digit year, transmit

[whatwg] [Selectors4] Linked Elements, was: required attribute in label

Someone on wha...@whatwg.org: This question is sort of CSS related, but I think it's worth bringing up here, assuming it hasn't already been discussed. I’m cross-posting to www-style, please follow-up there. [required]:after {content:*;} label for=name1Name/label input id=name1 type=text

Re: [whatwg] Please consider adding a couple more datetime input types - type=year and type=month-day

Ryosuke Niwa: All popular calendar systems should be supported. Browser widgets for the datetime types may support more than proleptic Gregorian, but the spec shouldn’t. ISO 8601 or a subset thereof should be the interchange format; clients and servers, before and after, may handle it

Re: [whatwg] input type=location proposals

Eitan Adler: 1) type=gps results in a (double?) text box which takes a latitude and a longitude What about elevation (e.g. floor in a skyscraper, airplane, ISS, submarine)? What about other planets and outer space? Somewhere between 8-| and ;-)

Re: [whatwg] HTML resource packages

Justin Lebar: Christoph Päper christoph.pae...@crissov.de wrote: Why do you want to put this on the HTML level (exclusively), not the HTTP level? If you reference an image from a CSS file and include that CSS file in an HTML file which uses resource packages, the image can be loaded

Re: [whatwg] [br] element should not be a line break

Jeremy Keith: The hr element is currently defined as a paragraph-level thematic break. I think br could be defined as a text-level thematic break. That makes perfect sense. The only problem I see is existing content which relies on consecutive ‘br’s producing multiple line breaks, i.e.

Re: [whatwg] HTML resource packages

Justin Lebar: We at Mozilla are hoping to ship HTML resource packages in Firefox 4, http://people.mozilla.org/~jlebar/respkg/ | html packages='[pkg1.zip img1.png script.js styles/style.css] |[static/pkg2.zip]' A page indicates in its html element that it uses one or more

Re: [whatwg] Headings and sections, role of H2-H6

Ian Hickson: On Fri, 30 Apr 2010, Nikita Popov wrote: Beyond that, using h instead of h1 would even be more backwards compatible to the HTML 4 use of headings. Actually, it would be less compatible, since it wouldn't render like a heading in older browsers. XHTML2’s ‘h’ is, especially in

Re: [whatwg] Simple Links

Ian Hickson: On Tue, 30 Mar 2010, Christoph Päper wrote: I wonder whether HTML could and should provide some sort of similar shortening, i.e. “a hrefFoo/a” or even, just maybe, “aFoo/a”. I later came to the conclusion that this might be a nice thing for HTML editors, but not for browsers

[whatwg] Sortable Tables

It’s a common task outside HTML to sort tables by one or more of its columns. There does seem interest among web content providers in making tables client-side sortable since there are several Javascript solutions to do just that, eg. http://meta.wikimedia.org/wiki/Help:Sorting,

Re: [whatwg] Sortable Tables

Peter Kasting: Why are you excluding datagrid, when that's the precise element aimed at addressing your issue? Because of r3555 http://lists.whatwg.org/htdig.cgi/commit-watchers-whatwg.org/2009/002723.html where it was removed and because I don’t think this requires a new element at all.

Re: [whatwg] RFC: input type=username

Eitan Adler: A type=username is added to the input element. type=username would MUST only be used for the name that is used to log in to the site. It MUST NOT be used for registration forms or anything else that requires a username. A form MAY have up to one (but not more) type=username

Re: [whatwg] Parsing RFC3339 constructs

Ian Hickson: On Tue, 11 Aug 2009, Nils Dagsson Moskopp wrote: Am Dienstag, den 11.08.2009, 07:27 + schrieb Ian Hickson: On Tue, 11 Aug 2009, Julian Reschke wrote: Ian Hickson wrote: - the literal letters T and Z must be uppercase It simplifies processing a tiny amount. So for a tiny

Re: [whatwg] About Descendent Tags

Ian Hickson: On Fri, 1 May 2009, Christoph Päper wrote: Ian Hickson: I've renamed the old header to hgroup. Did you consider using 'h' instead? I think that would be confusing for people who have heard of XHTML2's h (since it is quite different; HTML5's h1 is the better match

Re: [whatwg] About Descendent Tags

Ian Hickson: On Tue, 7 Apr 2009, Kristof Zelechovski wrote: The header element is not for the page header, it is for grouping section headings, and the tag name chosen for this element is misleading. I've renamed the old header to hgroup. Did you consider using 'h' instead?

Re: [whatwg] Vulgar fractions

Øistein E. Andersen: Currently, only a limited set of vulgar fractions can be expressed in HTML, viz, those that exist as pre-composed characters in Unicode. (...) 1) According to Unicode (...), `any sequence of one or more decimal digits, followed by the fraction slash [U+2044],

Re: [whatwg] [html5] Pre-Last Call Comments

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

[whatwg] Toggling Attributes

Ian Hickson (2009-02-13): There are three of these attributes so far: autocomplete = on/off contenteditable = true/false draggable = true/false It would be nice, actually, from an author perspective at least, if all of these worked for all applicable attributes: foo bar foo

Re: [whatwg] Safari-compatible input type=search

Andy Lyttle: results - if present, shows a little magnifying glass icon, which helps to visually identify the field as a search box The magnifying glass was a particularly poor choice by Apple[1], because icons featuring one usually represent zooming (in). Binoculars are (for some

Re: [whatwg] Placeholder option for text input boxes

Tab Atkins Jr.: 1) @placeholder Con: Duplicates semantics already present in label, (...) That could be circumvented by combining the two: labelFoo input type=text placeholder/label yielded [Foo ] whereas labelFoo input type=text placeholder=Bar/label resulted in [Bar

Re: [whatwg] object element feedback

Ian Hickson (2008-05-06): On Wed, 1 Nov 2006, Christoph Päper wrote: It's been a while, not that important anyhow. I think it would be helpful to /explicitly/ allow content types (...) in |type| of |object| to omit the subtype, e.g.: || object type=video data=foo.mpv/ ~= video

Re: [whatwg] Application deployment

Robert O'Callahan: http://www.example.com/site.jar#/path/inside/foo.html#heading1 URL parsing doesn't support multiple fragment identifiers I'm surprised that RFC 3986 (like 2396) makes '#' reserved in fragment identifiers (only '[]', too). The fragment ID is terminated only by the end

Re: [whatwg] Joined blocks

Shannon: Something I think is really missing from HTML is linked text Linked or continued (numbered, ordered) lists have been dicussed here a while ago, and were rejected if I remember correctly. They made a stronger use case than generic continued texts in my opinion, although both

[whatwg] [WF2] |min| and |max| number of selected |option|s

Dear WHAT WG When using input type=checkbox or select multiple one somtimes wants to limit the number of selected check boxes or options. I have no idea how to model this with |input|, but |select| could adopt the |min| and |max| attributes. They would not limit the content of

Re: [whatwg] Expanding datetime

Henri Sivonen: Date form widgets are meant for airline and hotel reservations What about, for instance, adjustable timelines at history websites or virtual skies at astronomic sites?

Re: [whatwg] HTML 5: The l (line) element

Ian Hickson: On Tue, 19 Feb 2008, Christoph P�per wrote: brfirst line/br Actually it's worse, /br is actually handled as br in browsers, so you'd end up with blank lines if we did this. Yeah, someone already told me by now. On the other hand, there are probably worse compatibility

Re: [whatwg] HTML 5: The l (line) element

Ian Hickson schrieb: On Wed, 23 Apr 2008, Christoph Päper wrote: there are probably worse compatibility issues with older specs and browsers than extra blank lines. Hopefully not in HTML5. :-) Isn't wrong numbering worse? HTML4 UA HTML5 UA ol reversed

Re: [whatwg] Feeedback on dfn, abbr, and other elements related to cross-references

the title= attribute on abbr required, and updated a bunch of examples. I hope you'll reconsider that decision. On Wed, 1 Nov 2006, Christoph Päper wrote: First off I think the requirement for a |title| is too strict, because there are time and space saving abbreviations everyone knows

Re: [whatwg] Feeedback on dfn, abbr, and other elements related to cross-references

Nicholas Shanks: I hope the following aids matters. Aids? :) Situations where expansions of abbreviations are needed: 1) People unfamiliar with the topic being discussed. This includes adhoc abbreviations, which I frequently use in table headers. 2) Documents that exist as

Re: [whatwg] Hyperlinks with |title| attribute

Nicholas Shanks: On 5 Apr 2008, at 11:57 pm, Ian Hickson wrote: On Sat, 5 Apr 2008, Christoph Päper wrote: Should (or may) user agents display the content of the |title| attribute of an |a| element in the GUI window caption (...), when the user followed the link and the retrieved resource

[whatwg] Hyperlinks with |title| attribute

Should (or may) user agents display the content of the |title| attribute of an |a| element in the GUI window caption (if the window manager used supports such), when the user followed the link and the retrieved resource is in a format that does not support specifying a title by itself

[whatwg] Listing element

The |listing| element is currently not defined in HTML5, but its parsing is said to be the same as for |pre|. Will |listing| be included some day or will it be left out, because |code| nested in | pre| provides the same semantics already?

Re: [whatwg] several messages

Ian Hickson (2008-03-23): On Tue, 18 Mar 2008, Christoph Päper wrote: a spanvalid non-negative integer/span greater than zero. Isn't that the description of a valid positive integer? If that term is not used or defined yet, why not? Because positive is confusing to people. Some people

Re: [whatwg] Commit-Watchers Digest, Vol 11, Issue 26

+ h4Attributes common to codetd/code and codeth/code elements/h4 + pThe codetd/code and codeth/code elements may have a dfn + title=attr-tdth-colspancodecolspan/code/dfn content + attribute specified, whose value must be a spanvalid non-negative + integer/span greater than zero. Isn't

Re: [whatwg] several messages about hr and related subjects

Ian Hickson: On Wed, 8 Jun 2005, Christoph Päper wrote: Ian Hickson: On Mon, 23 May 2005, Christoph Päper wrote: I almost didn't remember I was so vigorously against |hr|. Everything inside a 'div' belongs together somehow and everything that shares a class (...) is related to each other

Re: [whatwg] Some video questions

Charles: I was hoping that video would make Objecty http://wiltgen.net/ objecty/ redundant by making it easy for authors to embed video in a very simple, normalized fashion across formats, browsers and OSs. The |video| element in HTML5 will make it easy to embed videos (potentially

Re: [whatwg] Reverse ordered lists

Simon Pieters: It was pointed out to me that the start='' attribute (and the corresponding DOM attribute) currently defaults to 1. This could, AFAICT, reaonably trivially be changed to make it depend on the direction of the list and the number of li children. Or you would introduce an

Re: [whatwg] The truth about Nokias claims

2007-12-14 02:40 Ian Hickson: I do not believe anyone has suggested we use H.264 as the common codec. I would support it as *a* common codec, if it only /must/ be supported (transparently) when an underlying (plugin) framework, operating system or hardware provides it, and otherwise only

Re: [whatwg] [HTML5] 2.9.16. The samp element

2007-12-11 05:56 Ian Hickson: On Tue, 21 Mar 2006, Christoph Paeper wrote: Would the following be inadequate usage according to this specification? a href=foo.imgsampimg src=foo.t.img alt=...//samp/a Yes. The former would be appropriate if a computer output the given image and that

Re: [whatwg] simple numbers

2007-12-11 06:20 Ian Hickson: I considered all the feedback on having a number element (or similar), quoted below. While I think there is certainly something to be said for the proposal, I don't think there is enough evidence that authors really want or need this. JFTR:

Re: [whatwg] on codecs in a 'video' tag.

Anne van Kesteren: Also, I think the HTML specification should mandate (as SHOULD- level requirement, probably) support for the various supported image formats as it gives a clear indication of what authors can rely on and what user agents have to implement in order to support the web.

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

Henri Sivonen: On Oct 30, 2006, at 22:33, Ian Hickson wrote: The CSS community has requested a date or time element because they want to restyle dates and times according to locale. Then the recent request to www-style for styling numbers would be justified as well. An element for times

Re: [whatwg] video element feedback

Kornel Lesinski: http://example.com/[EMAIL PROTECTED]:35 that would cause UA to start playing the embedded video.ogg from 12:35. That would limit documents to one |video| (or |audio|) element.

Re: [whatwg] video element feedback

Håkon Wium Lie: Also sprach Martin Atkins: If video is going to be considered a first-class citizen, I argue that this needs to be possible for video as well: video src=pretty.ogg.../video Right. I think I agree with you. Perhaps we can encourage implementors to add a simplistic UI in

Re: [whatwg] Video (Was: How not to fix HTML)

*Ian Hickson*, 2006-10-30: Sure. FWIW, there's a lot of interest in browser vendors about introducing a video element or some such (or maybe making browsers natively support video in object, or both). I think it would be helpful to /explicitly/ allow content types (alias media types)

Re: [whatwg] Joe Clark's Criticisms of the WHATWG and HTML 5

*Henri Sivonen*, 2006-10-29: http://blog.fawny.org/2006/10/28/tbl-html/ * HTML has samp, var, and kbd. I use all of them and I am pretty much the only one who does. FWIW, I think samp and kbd don't deserve to be in HTML and I am not convinced that the use cases for var could not be

[whatwg] [HTML5] Editorial: 3.10.18. The |sup| and |sub| elements

The second to last example should probably better read: varE/var = varm/var · varcvarsup2/sup or maybe, as the speed of light is a constant, varE/var = varm/var · csup2/sup.

Re: [whatwg] return lowercase hex values for fillStyle and strokeStyle

*Anne van Kesteren*: Instead of returning an uppercase six digit hex value I suggest returning a lowercase value for compatibility with what UAs (including IE) currently do It may be the right decision on compatibility grounds, but other than that lowercase hexadecimal digits (0-9, a-f)

Re: [whatwg] Modal Dialog Box support

*Anders Rundgren*: But it is very hard to create certain types of applications without having modal dialogs. That does not mean modal dialogs were a good idea, ever.

Re: [whatwg] text/html conformance checkers and comments

Lachlan Hunt: ! As useless as the first one may be, Well, it's shorter than !--sic!--, i.e. usable for source code emphasis.

Re: [whatwg] attribute value normalization

Anne van Kesteren: It should basically not happen at all. It appears that no browser has implemented the 'may' from HTML4 That's the logic of tagsoup parsers, i.e. their inconsistency regarding authoring sloppiness. If it had been should not, they would probably do it. ;) Did you also try

Re: [whatwg] WA1: meta attribute requirements

Ian Hickson: The difficulty is in walking the fine line between useful and over-constrained. For example, the fact that ol/ol is invalid in HTML4 is a real problem. Well, olliThis list item will be replaced by a script./ol is not invalid. An empty list doesn't make any sense otherwise,

[whatwg] Suggesting a 'transpose' Attribute for Tables

column-progressive despite 'tr' meaning table row; it includes the row-groups ('thead', 'tfoot' and 'tbody'). Actually I am not sure whether it is not too presentational and thus would better be done in CSS. Christoph Päper

Re: [whatwg] [WF2] Comments on sections 2.3 -- 2.5

Lachlan Hunt: I just did a google search and found some references [1] stating that ISO 8601:1988 and ISO 8601:2000 have been withdrawn and replaced with ISO 8601:2004. I'm not sure what the differences are (I haven't read through the whole article yet), though it looks like the basic date

Re: [whatwg] Re: About XHTML 2.0

Matthew Raymond: Christoph Päper wrote: The div (as well as span) does indeed have semantic meaning in that it can group things. However, in the case of replacing hr, I don't see how this semantic information can actually be used to benefit the user. It's certainly useless on modern

Re: [whatwg] Re: About XHTML 2.0

Sorry for the late reply, I had to read the whole thread in www-html first and was away for a few days. Ian Hickson: On Mon, 23 May 2005, Christoph Päper wrote: Ian Hickson: section div class=pov Foo.../div ... ...has no semantics apart from delineating one section. Remember

Re: [whatwg] Re: About XHTML 2.0

Ian Hickson schrieb: I read a lot of fiction books and when I come across a * * * it reads to me like a paragraph, saying Meanwhile, in a different part of the universe:; it doesn't read as end section. new section:. section ... div class=pov Foo.../div !-- 'plot', 'note',

Re: [whatwg] Web Forms 2.0 Feedback

*Ian Hickson [EMAIL PROTECTED]*: abbrMsuplle/sup/abbr varxsub2/sub/var I'm not sure how to deal with the chemistry case. We don't really have an element for anything like chemical formulas. Stretching its semantics really far, one could use 'code' for formulas¹ and 'abbr' for isotopes etc. ¹

Re: [whatwg] [html5] DI element

*Anne van Kesteren* [EMAIL PROTECTED]: The advantage of DI is that it allows grouping of definitions ACK and therefore takes away the importance of element order. So you want to put 'dt' after 'dd'? Seems strange to me. From a structural point of view it is very difficult for current DL element