On 5/3/13 7:07 PM, Christian Biesinger wrote:
fantasai pointed out that CSS does specify this:
"If the box does not have a baseline, align the bottom margin edge
with the parent's baseline."
(http://www.w3.org/TR/CSS2/visudet.html#propdef-vertical-align)
Yes, but that _if_ the box does not have
On Tue, 13 Nov 2012, Jeff Muizelaar wrote:
>
> We have recently implemented isPointInStroke(x,y) in Firefox
> (https://bugzilla.mozilla.org/show_bug.cgi?id=803124). This is a
> parallel to isPointInPath(x,y) and returns true if the point is inside
> the area contained by the stroking of a path.
fantasai pointed out that CSS does specify this:
"If the box does not have a baseline, align the bottom margin edge
with the parent's baseline."
(http://www.w3.org/TR/CSS2/visudet.html#propdef-vertical-align)
Sounds like there's a bug in Firefox and (still) in Chrome dev.
-christian
On Thu, Apr
> http://html-differences.whatwg.org/
Thanks Simon!
Unrelated to the rest of the conversation, could we reconsider whether
every version of this document needs to list *all* document-internal
changes, in section 6?
I’d argue it suffices to list the changes to the last version of the
document. Th
Xaxio wrote:
> If you believe that documenting the (constantly evolving) differences
> between HTML and its HTML5 and HTML5.1 subsets would be relevant, please do
> so! It would be a great thing to be able to reference such a document.
I have made a start on a document
http://www.w3.org/wiki/
>
> No, it only says *that* it uses "HTML" to refer to "the W3C HTML5
> specification, W3C HTML5.1 specification, and the WHATWG HTML standard".
> *Why* it does so is not addressed at all
You are correct. The "why" is something that should be addressed. Perhaps
the document could read:
This do
2013-05-03 21:19, Xaxio Brandish wrote:
Ah. The document scope [1] explains why it uses "HTML" in the title as
opposed to HTML5 or HTML(5).
No, it only says *that* it uses "HTML" to refer to "the W3C HTML5
specification, W3C HTML5.1 specification, and the WHATWG HTML standard".
*Why* it doe
I see what you're saying.
The document title on the WHATWG site is titled based on the W3C document
[1]. However, I see no reason to keep the same title structure; it will be
easy to find either way.
In that case, "Differences between HTML and HTML4" sounds nice as well.
The only reservation I h
It is my understanding that the W3C version lists "HTML5" and the
WHATWG version uses "HTML". That was what I intended by "HTML(5)". I
didn't mean the parentheses were included literally.
Gordon
On Fri, May 3, 2013 at 2:19 PM, Xaxio Brandish wrote:
> Ah. The document scope [1] explains why it u
Ah. The document scope [1] explains why it uses "HTML" in the title as
opposed to HTML5 or HTML(5).
--Xaxio
References:
[1] http://html-differences.whatwg.org/#scope
On Fri, May 3, 2013 at 11:16 AM, Gordon P. Hemsley wrote:
> The way I interpreted it, Jukka meant that the title could be
> som
The way I interpreted it, Jukka meant that the title could be
something more flowing, like "Differences between HTML4 and HTML(5)".
Gordon
On Fri, May 3, 2013 at 2:10 PM, Xaxio Brandish wrote:
> Good day,
>
> Let us start with a definition:
>
> es·o·ter·ic
> /ˌesəˈterik/
> Adjective
> Intended f
Good day,
Let us start with a definition:
es·o·ter·ic
/ˌesəˈterik/
Adjective
Intended for or likely to be understood by only a small number of people
with a specialized knowledge or interest.
The document Simon delivered and formatted is useful to a wide range of
audiences interested in HTML and
On Fri, May 3, 2013 at 2:23 AM, Anne van Kesteren wrote:
> On Thu, May 2, 2013 at 10:49 PM, Rik Cabanier wrote:
> > Reading the Origin spec [1]:
> >
> > For fonts:
> >
> > The origin of a downloadable Web font is an alias to the origin of the
> > absolute URL used to obtain the font (after any r
alonn schrieb am Fri, 3 May 2013 18:50:36 +0300:
> 1. Having a way to check for the current permission without
> initiating a new Notification object first. something like webkit has
> (I'm not sure it's not deprecated)
> window.webkitNotification.checkPermission() I saw this isn't in the
> api,
On Fri, May 3, 2013 at 4:48 PM, alonn wrote:
> 1. Having a way to check for the current permission without initiating a
> new Notification object first. something like webkit has (I'm not sure it's
> not deprecated) window.webkitNotification.checkPermission()
> I saw this isn't in the api, and I t
2013-05-03 18:37, Simon Pieters wrote:
The past few days I've been working on updating the HTML differences
from HTML4 document, which is a deliverable of the W3C HTML WG but is
now also available as a version with the WHATWG style sheet:
http://html-differences.whatwg.org/
I think you should
I played a little bit with the Notification API and I have a couple of
suggestions (I tried the chrome implementation with Mozille hacks jsFiddle
http://jsfiddle.net/robnyman/TuJHx/) for improvement (at least
in my view) or a more consistent API as web developer:
1. Having a way to check for the c
I played a little bit with the Notification API and I have a couple of
suggestions (I tried the chrome implementation with Mozille hacks jsFiddle
http://jsfiddle.net/robnyman/TuJHx/) for improvement (at least
in my view) or a more consistent API as web developer:
1. Having a way to check for the c
Hi
The past few days I've been working on updating the HTML differences from
HTML4 document, which is a deliverable of the W3C HTML WG but is now also
available as a version with the WHATWG style sheet:
http://html-differences.whatwg.org/
Review welcome. Please file bugs.
--
Simon Pieters
On Fri, May 3, 2013 at 3:07 PM, Boris Zbarsky wrote:
> The text at
> http://dev.w3.org/csswg/css-fonts/#default-same-origin-restriction and
> http://dev.w3.org/csswg/css-fonts/#allowing-cross-origin-font-loading
> predates your introduction of the mode values, but clearly corresponds to
> the "COR
On 5/3/13 5:23 AM, Anne van Kesteren wrote:
On Thu, May 2, 2013 at 10:49 PM, Rik Cabanier wrote:
What do you mean by that? Is this underspecified?
CSS should say it fetches using mode CORS. That will result in a
either a response marked CORS-same-origin or a network error. Fonts
can be then b
On Thu, May 2, 2013 at 10:49 PM, Rik Cabanier wrote:
> Reading the Origin spec [1]:
>
> For fonts:
>
> The origin of a downloadable Web font is an alias to the origin of the
> absolute URL used to obtain the font (after any redirects). [CSSFONTS]
>
> The origin of a locally installed system font i
On 2013-05-03 08:29, Gray Zhang wrote:
>> Not sure if WHATWG is doing anything, but in the W3C there
ishttps://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html
in the Web Apps group
> ...
>
> How would it behave if my web app requests orientation locking but is
placed in an `` elem
23 matches
Mail list logo
