quoted text.)
Again, is this something the SVG WG is willing to do?
Thank you,
Hugh
On Thu, Dec 22, 2011 at 7:28 AM, Hugh Guiney hugh.gui...@gmail.com wrote:
Cameron McCormack forwarded this proposal to public-svg-wg a year ago
(thanks, Cameron!) but no one commented on it, so I'm reposting
On Thu, Nov 15, 2012 at 8:21 PM, Eitan Adler li...@eitanadler.com wrote:
Actually, there's a good point: I would actually add this: if main or
an
element with @role=main exist on the page, there is no need to run the
Scooby-Doo algorithm and that element can just be chosen as the main
As a developer I'm in favor of this. Just take a look at the how
popular the question of How do I enable Reader mode is on SO[1], and
how complex and mysterious the actual algorithm appears to be[2], and
it's evident how authors and implementors alike could benefit from a
dedicated element.
On Wed, Oct 17, 2012 at 7:23 PM, Ian Hickson i...@hixie.ch wrote:
I haven't added this, because contenteditable= is only truly useful with
scripting enabled, and it's basically one line of script to support
shunting the current value into a hidden input.
For me, it's also useful even just as
My use case: I have a div with overflow: hidden that contains slides
as part of a JavaScript carousel. It has to be overflow: hidden
because otherwise the unseen slides are visible/stretch the page. And
because each slide is different, the containing div therefore needs
to grow/shrink in height
Just saw the following change: http://html5.org/r/7347, and while it's
certainly nice to have examples, I don't understand why rel=tag
*always* applies to the whole document. I think it makes perfect sense
in the first example, but my expectation as an author would be for
tags within articles to
Didn't mean to go off-list with this. Posting the prior exchange
before I respond:
On Fri, Sep 14, 2012 at 7:36 PM, Hugh Guiney hugh.gui...@gmail.com wrote:
On Fri, Sep 14, 2012 at 5:03 PM, Ian Hickson i...@hixie.ch wrote:
Because it was invented before article, so consumers apply
On Fri, Sep 14, 2012 at 9:51 PM, Ian Hickson i...@hixie.ch wrote:
Also, as I pointed out in the original post, consumers already use
rel=tag intending for it to apply only to portions of a page.
Consumers or producers? What matters here is not changing _consumer_
behaviour, so that we don't
I'm developing a CMS and would like to be able to submit user-edited
content back to the server, but at present, it's not possible to do
this without copying the contents of the edited element with
JavaScript into, say, a hidden form field. I think that there should
be some mechanism to associate
On Mon, Apr 30, 2012 at 7:37 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 28 May 2010, Ian Fette wrote:
Has any thought been given to exposing such metrics as framerate, how
many frames are dropped, rebuffering, etc from the video tag?
It has come up a lot, but the main question is: what is
I am confused by the current definition of outline depth (
http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#outline-depth),
which, if I understand it correctly, states that the depth resets with each
sub-outline.
So, in the following:
body
h1Document Title/h1
section
On Mon, Mar 26, 2012 at 8:08 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
What text are you looking at that implies the outline depths of the
headings in the first snippet are all 1?
I could not find anything, but the person who wrote that JavaScript
implementation seemed pretty convinced
On Mon, Mar 26, 2012 at 8:30 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
It's possible they'd gotten confused by the fact that the first
heading in a section, no matter what rank it is, is more-or-less
equivalent to a h1 as far as the outlining algorithm is concerned.
Actually his stated
On Mon, Mar 12, 2012 at 8:52 PM, Ian Hickson i...@hixie.ch wrote:
The validator is probably just not up to date.
Note that that in this case the validator is probably right. If it's just
presentational, why are you using h2? It doesn't seem presentational to
me. I think you are incorrectly
Why not?
I have this in an otherwise-valid HTML5 + SVG 1.1 + MathML 2.0 + RDFa
Lite 1.1 document:
hgroup
h1Company Name/h1
h2 role=presentationTagline/h2
/hgroup
Spec says:
Authors must not set the ARIA role and aria-* attributes in a manner that
conflicts with the
semantics described
On Fri, Feb 3, 2012 at 3:22 PM, Ian Hickson i...@hixie.ch wrote:
There are a number of places in HTML where it would be nice to be able to
group things together -- just look at how often people stick divs in
their pages for no purpose whatsoever other than styling.
This shouldn't be
On Sun, Mar 4, 2012 at 5:07 PM, Ian Hickson i...@hixie.ch wrote:
Then why is section in the spec?
To make it easier to move subsections around without having to change all
the h5s to h4s and so forth.
That's it? So the fact that it provides explicit grouping and styling
are unintentional
On Mon, Mar 5, 2012 at 12:09 AM, Ian Hickson i...@hixie.ch wrote:
The only thing it adds to the grouping is the ability to have a subsection
that is then followed by more content from the subsection's parent
section. You couldn't do that with hx alone. However, for section
that's more of a
On Sat, Feb 11, 2012 at 7:47 AM, Benjamin Hawkes-Lewis
bhawkesle...@googlemail.com wrote:
Doesn't the spec imply it should?
That depends on whom you ask. I would think that it does, but since it
doesn’t explicitly say to parse alternative text for replaced
elements, implementors could simply
Currently when I run markup like this through outliner programs, they
return blank section titles:
h1img src=/img/logo.png alt=Company Name //h1
h1
svg
g
titleCompany Name/title
path /
…
/g
/svg
/h1
I feel that in both instances, Company Name should become the
I'm currently creating a custom HTML video player UI. What I'm trying to
achieve is a seek bar control—a horizontal slider that allows the user to
seek to a specific point in time. Right now the basic functionality of this
can be achieved using a range input with a max value set to the video's
On Tue, Jan 10, 2012 at 2:52 AM, Jordan Dobson jordandob...@gmail.com wrote:
Sounds like what you want is flex box. Have you looked at that yet?
I don't know flexbox too well yet—how would one use it to create a
columnar dl? From what I can tell though, it still wouldn't allow me
to style dt/dd
As I understand it, the main reason for rejecting di was that it
solves a problem that is allegedly CSS's job, but as an author who
uses dls quite extensively, adding a grouping element would really
make my life a lot easier.
Yes, my most common problem with dls is styling them, but it's
hardly
, 2010 at 9:35 PM
Subject: Re: [whatwg] Allow Select SVG Elements In head
To: Hugh Guiney hugh.gui...@gmail.com
Cc: whatwg wha...@whatwg.org
On Fri, 27 Aug 2010, Hugh Guiney wrote:
I'm authoring an XHTML host document with namespaced inline SVG and
XLink. I have vector images that recur throughout
Hey All,
I was in the process of coding a prototype for a site I'm working on
when I decided that certain nav's should actually be menu's.
While the basic concept is apparent, unfortunately, with zero browser
implementation at this time, it is impossible to actually know what my
markup is doing
I am authoring a video portfolio page using Kroc Camen's Video For
Everybody code http://camendesign.com/code/video_for_everybody for
each piece. In this code he includes a download section for users who
may be unable to play the video live on the site, e.g. because they
lack both HTML5 (or the
I am using noscript as permitted, In a head element of an HTML
document, if there are no ancestor noscript elements. but still
getting an error from Validator.nu saying it's not allowed.
Settings:
Encoding: as set by server/page
Schemas: http://s.validator.nu/xhtml5-aria-rdf-svg-mathml.rnc
I'm authoring an XHTML host document with namespaced inline SVG and
XLink. I have vector images that recur throughout the site. I'd like
to implement SVG's defs and use to reduce the file size of the
document and keep style separate from content, as with CSS.
If I put an SVG tree with defs
Thanks for your insight Silvia.
On Wed, Feb 10, 2010 at 2:47 AM, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
Firstly, I think that explicit user choice isn't a problem.
As a content provider, you have several means of doing this user choice:
1) You can provide in a single (admittedly
On Mon, Feb 15, 2010 at 7:07 PM, Tim Hutt tdh...@gmail.com wrote:
Erm, what? The 360p refers to the 'native' resolution of the video
file youtube sends. If you play a 360p video fullscreen, it's still
only got 360 lines; they're just scaled up. It would be meaningless if
the number referred to
On Mon, Feb 15, 2010 at 8:09 PM, David Singer sin...@apple.com wrote:
I think I agree with Tim here. When you ask to watch 360p content, you are
asking for content that has 360 lines of pixels to be displayed to you.
Right.
You're not asking for whatever is displayed to you to occupy only
On Tue, Feb 16, 2010 at 12:35 AM, Gregory Maxwell gmaxw...@gmail.com wrote:
...
Pixel aspect ratios.
This whole discussion has been painful to watch.
I know what pixel aspect ratios are. All too well, actually—for
instance, the square-pixel equivalent of 720x480 widescreen can be
either
On Mon, Dec 14, 2009 at 4:08 AM, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
I would almost consider simply using low quality and high quality
as quality distinguishers (and maybe medium) and leave the actual
choice of encoding to the hosting entity. Right now, may sites provide
only two
On Sun, Dec 13, 2009 at 7:26 AM, Aryeh Gregor simetrical+...@gmail.com wrote:
JavaScript is an integral part of HTML to all intents and purposes.
HTML itself does not and should not try to cover use-cases that are
already adequately covered by HTML+JavaScript -- there will always be
things
Hey all,
So, in my first foray into preparing Theora/Vorbis content, for use
with video, I realized that I wasn't sure with what settings to
encode my materials. Should I:
A.) Supply my visitors with the best possible quality at the expense
of loading/playback speed for people on slower
I concur 100%.
Additionally, I don't understand why the time element is allowed to specify
an arbitrary hour, but not an arbitrary month or year.
My own use case involves marking up years of publication for documents I
have created, to be displayed in an online resume that can be sorted by
date.
On Thu, Dec 10, 2009 at 9:06 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Are you planning on using the information in time to *do* the
sorting? That is, when someone chooses sort by date, do you have
scripting that searches in each section for a time and extracts the
date to determine
On Tue, Dec 1, 2009 at 7:08 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
The @caption proposal isn't for an attribute on p only, but rather
for an attribute on any element that is a child of a figure. (It's
just that most of the time using a p is most appropriate.)
Ah, OK. Well, given the
Is there a reason we can't reuse legend (or label)? I don't think
giving p an attribute that it can only use inside of figure is
very straightforward.
On Tue, Oct 6, 2009 at 6:33 PM, David Workman workm...@gmail.com wrote:
I don't know about others, but that just looks ugly to me (the repetition of
'cite' looks unnecessary). I know elegance isn't crucial, but given the
choice between cite for= and cite cite= I'd go for the former.
As a
On Wed, Oct 7, 2009 at 6:51 PM, David Workman workm...@gmail.com wrote:
I agree that href would be better than src due to the reasons you gave.
However, rather than adding a new attribute of alias, could cite instead
be given a name attribute that works similar to radio button names in forms
On Tue, Oct 6, 2009 at 4:15 PM, Erik Vorhes e...@textivism.com wrote:
I suppose a allows for more functionality in current UAs, but this
is an interesting proposition, especially if there were a way to
crosslink cite used in this way to the original source (or whatever
it would point to).
42 matches
Mail list logo
