es for registerProtocolHandler is
based on the following set of preferences:
https://searchfox.org/mozilla-central/search?q=network.protocol-handler.external=
by the implementation which I believe lives here:
https://searchfox.org/mozilla-central/source/browser/components/feed
EXIF support, and there may be a dependency on
that), but once the developer has opted in, everything should really
act like the rotation is part of the image format.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla https
Transitions. (This one is minor.)
As I said, though, figuring out how I'd want the spec to address (1)
and (2) is a rather large task; it requires carefully looking at the
other things that interact with these things.
-David
--
턞 L. David Baron http://dbaron.org
in the imagemap shouldn't change as a result of CSS styling of the
image.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla https://www.mozilla.org/ 턂
Before I built a wall I'd ask to know
What I was walling
/007236.html
I'd be happy to see somebody drive a solution to this forward.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla https://www.mozilla.org/ 턂
Before I built a wall I'd ask to know
What I
/core.html#Core-DOMTimeStamp
[2] http://www.w3.org/TR/hr-time/#sec-DOMHighResTimeStamp
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla https://www.mozilla.org/ 턂
Before I built a wall I'd ask to know
What I
br
implementation and replacing it with the above.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla https://www.mozilla.org/ 턂
Before I built a wall I'd ask to know
What I was walling in or walling out
the language for:
* font selection
* language-specific text-transform behavior
* hyphenation (which doesn't work unless it's explicitly specified,
as required by http://dev.w3.org/csswg/css-text/#hyphens-property )
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢
to block containers, which display:ruby is not.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
On Sunday 2013-02-17 11:35 -0600, Glenn Maynard wrote:
On Mon, Jan 21, 2013 at 8:39 AM, L. David Baron dba...@dbaron.org wrote:
But I think it's a large amount of extra implementation complexity
to honor @-rules whose purpose is to build global dictionaries (in
particular, @keyframes
On Monday 2013-01-21 11:17 -0800, Tab Atkins Jr. wrote:
On Mon, Jan 21, 2013 at 6:39 AM, L. David Baron dba...@dbaron.org wrote:
Thus I think the specification should mandate that @keyframes and
@font-face are ignored in scoped style sheets, just like @page.
I think it would also be good
unacceptable to have a computed value that's not
specifiable in CSS; it breaks basic ideas of round-tripping and the
CSS OM.
(3) Is there a way to get notified when new CSS features are added
to the HTML spec? I only happened to stumble across this one.
-David
--
턞 L. David Baron
if the specification left the effects
of unknown @-rules undefined until whether they should be supported
can be properly considered.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
value
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
)?
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
.)
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
for
font-size was documenting the exception (that the quirk *does*
apply) for *within* the 'font' shorthand.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
to be handled between font-weight and font-size), and then
the shorthand is syntactically invalid because it doesn't have a
font-size. I don't see any reason to fix that.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http
in the future. (Consider, for example, 'fade'.)
More importantly, though, if Gecko encounters an ambiguity between
color and keyword in a property that accepts both, it will pick the
keyword.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla
.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
or others could
probably answer questions you have about how it works and how to
understand it.
I'm not the right person for pointers to other implementations,
though.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http
.
It surprises me greatly that Gecko doesn't treat unicode as an alias
for utf-16.
Why? If it's not needed, why shouldn't WebKit and IE drop it?
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
because pages
that work for one user don't work for another.
I'm just not quite sure how to get from here to there, though, since
such changes are likely to make users experience broken content.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla
On Thursday 2011-12-01 14:37 +0900, Mark Callow wrote:
On 01/12/2011 11:29, L. David Baron wrote:
The default varies by localization (and within that potentially by
platform), and unfortunately that variation does matter.
In my experience this is what causes most of the breakage. It leads
to be notified or if that
developer is the person who requested the change in the first place.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢 Mozilla http://www.mozilla.org/ 턂
if the algorithm here changed,
and I'd really rather not add that support for a legacy feature, nor
would I like to have an inconsistency between CSS and HTML as to
whether system colors are dynamically updated.
-David
--
턞 L. David Baron http://dbaron.org/ 턂
턢
- Applications - mailto so they don't even need to
bother registering themselves.
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
.
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
On Monday 2010-08-30 14:28 +0200, Anne van Kesteren wrote:
On Sun, 29 Aug 2010 15:01:27 +0200, L. David Baron
dba...@dbaron.org wrote:
On Wednesday 2010-08-25 10:28 +0200, Anne van Kesteren wrote:
We need a feature for case-insensitive matching in Selectors already
for XHTML (if we really
are).
If it weren't ASCII-only, it would involve significantly more
complexity than what's needed to support HTML.
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
to
expose to authors.
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
in CSS
but static in HTML.
What was the motivation for adding support for CSS2 system colors
(which I would note are deprecated in css3-color) to legacy HTML
color values? What implementations support them, and do they
respond to dynamic changes properly?
-David
--
L. David Baron
clearly shows that it's the intent of css3-selectors that the
pseudo-class apply in this case.
From looking at VCS history, Gecko has implemented :checked on
option elements since Gecko 1.8 == Firefox 1.5.
-David
--
L. David Baron http://dbaron.org/
Mozilla
particularly strongly about this one, but it seems like
the original intent of :default was to match both things that are
the default button and things that are selected by default.
Was this difference with existing implementation behavior
intentional?
-David
--
L. David Baron
that allows user agents to be
more flexible than requiring that all of the elements listed match
exactly one of :link and :visited.
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
On Friday 2010-04-30 13:05 -0700, Tab Atkins Jr. wrote:
On Fri, Apr 30, 2010 at 12:12 PM, L. David Baron dba...@dbaron.org wrote:
For a long time, Gecko has implemented the behavior that the
:default pseudo-class matches checkboxes, radios, and options that
are selected by default (i.e
On Friday 2010-04-30 13:43 -0700, L. David Baron wrote:
On Friday 2010-04-30 13:05 -0700, Tab Atkins Jr. wrote:
On Fri, Apr 30, 2010 at 12:12 PM, L. David Baron dba...@dbaron.org wrote:
For a long time, Gecko has implemented the behavior that the
:default pseudo-class matches checkboxes
believe I've seen UI that does this, although I can't think
where.)
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
selectors that let authors easily improve them?
(Why?)
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
) and with the clear intent of
XHTML1, and doesn't seem implementable on top of a conformant CSS
selectors implementation.
Do we really want to do this?
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
gradually turn them into something that requires 15-year-old
software to read.
For more information (and the reason that prompted me to post here),
see https://bugzilla.mozilla.org/show_bug.cgi?id=452915 .
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation
the comment I wrote at
http://hg.mozilla.org/mozilla-central/file/4cabe72ad940/layout/style/nsCSSPseudoElements.h#l50
, and note that it mentions a third intermediate category, in which
some proposed XForms pseudo-elements, and perhaps some future
pseudo-elements, would fit.)
-David
--
L. David
, and partly since it's a lot simpler
(maybe not to implement in one engine, but probably to implement
interoperably and to specify, since you need to be careful about
what applies and doesn't apply to the pseudo-element).
-David
--
L. David Baron http://dbaron.org
On Thursday 2010-02-18 17:40 -0500, L. David Baron wrote:
I'd be inclined towards the pseudo-class, though, partly since that
failure mode bothers me less, and partly since it's a lot simpler
(maybe not to implement in one engine, but probably to implement
interoperably and to specify, since
pseudo-element (styles that don't select the pseudo-element don't
change the UA default), but with the addition that authors can style
the input in other ways.
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http
:
-BEH
WER
whereas the markup:
HEB-pREW
looks like:
BEH-
WER
(the hyphen appears at the opposite end).
-David
[1] http://unicode.org/reports/tr9/
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
may not expect the act of
uploading a file to give the Web site details of their file system
structure. There also seems to be some concern that those details
may provide information useful to an attacker.
-David
--
L. David Baron http://dbaron.org/
Mozilla
. (For other platforms, change Tools
- Options to Edit - Preferences (GNOME-based platforms) or Firefox
- Preferences (Mac).)
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
. However, I
think HTML5 specification reflects significant consideration for the
needs of disabled users, and I strongly encourage more input
regarding use cases for and requirements of disabled users that the
specification fails to meet.
-David
--
L. David Baron
.
(You didn't have any autodetection enabled, did you?)
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
On Wednesday 2009-02-11 08:39 +, Ian Hickson wrote:
On Thu, 10 May 2007, L. David Baron wrote:
The interaction of area elements with CSS styling is not defined in HTML
5. Since area elements are particularly unusual (in that they appear an
arbitrary number of times, whenever
# committee are currently:
#
# [...]
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
=explicitmindate=1998-01-01maxdate=1999-01-01cvsroot=%2Fcvsroot
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
makes sense.
What was the actual use case you were trying to solve with this
attribute?
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
useful than an
attribute that simply prevents scripts from executing, and it avoids
introducing similar-looking attributes that actually behave very
differently.
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
this ought to be defined (although if it
were defined by making a more general statement of equivalence that
might be good, since I suspect a bunch of other similar things are
undefined as well).
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation
fall back to 'ltr' as a last resort.
However, as an intermediate step, it might be worth falling back to
the direction property of the root element (if present) of the
canvas element's ownerDocument.
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation
for every text operation (probably the latter).
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
.)
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
bugs handling dynamic changes. Although we probably already
break it in a bunch of ways as well.)
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
(but for hyperlinks, at the time it is dereferenced). That is easy to
That would make whether :link or :visited matches not correspond to
what you get when you click on the link, which seems pretty bad.
Hyperlinks already need to be resolved eagerly to style links
properly.
-David
--
L. David Baron
. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
://www.whatwg.org/specs/web-apps/current-work/multipage/section-video.html#video
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
shouldn't they also be the
mappings in HTML5?
-David
--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/
pgp6HCOm05g1A.pgp
Description: PGP signature
On Sunday 2007-07-01 23:40 +0200, Øistein E. Andersen wrote:
L. David Baron wrote:
What's wrong with these mappings, and why shouldn't they
also be the mappings in HTML5?
The problem is that they are canonically equivalent to CJK characters.
Makes sense. I think I misread your original
,
although appendRule would be nice), and insertRule takes the rule as
a single string, not a separate selector and declaration.
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgplDMpa2iv1v.pgp
this for a elements as used in image maps,
but I think that's been removed from HTML 5.)
Some comments about the behavior of other browsers (with testcase)
are available at [1].
-David
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=302536#c58
[2] http://www.w3.org/TR/css3-ui/
--
L. David Baron
,
Nokia has shipped more digital cameras than anyone else (really). In
I don't think shipped implementation count is a useful metric here.
What matters is the amount of use. I think the average PC is used
for a lot more Web browsing than the average high-end cell phone.
-David
--
L. David Baron
On Wednesday 2007-03-14 15:20 +0100, Peter Karlsson wrote:
L. David Baron on 2007-03-13:
I tend to think it would be good that new uses of URIs/IRIs document that
they are really IRIs and therefore this reverse-encoding behavior should
not be used, but instead encoding should be done
when browsing East
Asian Web sites. We avoid changing our interpretation of Web
standards based on localization; that's just too much complexity to
test and maintain.
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla
is not a license.)
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgpIdPblKaQPz.pgp
Description: PGP signature
On Sunday 2007-03-11 18:26 +0100, Bjoern Hoehrmann wrote:
* L. David Baron wrote:
My dismissal of XHTML is that the designers of XHTML and related
standards are repeatedly introducing more and more incompatibility
between XHTML and HTML, which makes it progressively harder for
authors
spelling is correct.
-David
[1] http://www.w3.org/People/Quin/
[2] http://htmlhelp.com/~liam/
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgpVDa5ExYuRi.pgp
Description: PGP signature
ever
occurring. And if that transition is never going to occur on a
large scale, why worry about it?
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgpEGHw5cO4FD.pgp
Description: PGP signature
be the most useful fallback content
available. Insisting that those captions not be available when
there is no fallback content seems like a bad idea.
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
On Friday 2006-07-21 09:07 -0700, L. David Baron wrote:
On Friday 2006-07-21 11:14 +0300, Henri Sivonen wrote:
I gather that a normative reference to the Porter–Duff paper is needed:
http://keithp.com/~keithp/porterduff/p253-porter.pdf
Perhaps, assuming that's what's been implemented
in the spec. But that paper doesn't
define binary operators for 'darker' and 'lighter', which seem to be
among the less-interoperable right now. (It defines a unary 'darken'
operator over a space of numeric parameters.)
-David
--
L. David BaronURL: http://dbaron.org
objects (e.g., strings in JavaScript).
I don't think this pattern makes sense for mutable objects. It just
suggests immutability. And making the canvas context objects immutable
doesn't really make sense without much more significant changes.
-David
--
L. David Baron
. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgpp9ZvKOeoW7.pgp
Description: PGP signature
) or blank (latest for 10.4/Intel).)
Looking at Mozilla's code, it implements copy and source-over as the
same thing; from the code I'd guess that source-over was the incorrect
one, and this test seems to agree.
-David
--
L. David BaronURL: http://dbaron.org
On Friday 2006-06-09 00:42 +, Ian Hickson wrote:
On Wed, 31 May 2006, L. David Baron wrote:
I don't see why the same attribute _shouldn't_ be used to determine
the type of data to allow, and whether to do spell checking or not.
After all, whether to spell-check is directly
would you propose instead?
I think it is an option, and I don't see why you're so insistent that it
isn't. Authors are actually going to want interoperability; to get
that, it's required.
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead
. Overloading that to get a boolean for whether
spellchecking should be enabled seems broken.
I'd rather see a new attribute for this.
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgpW1qXwiBsEF.pgp
Description
we're past that point, unless you want to invent a syntax that
represents MIME type - parameter list pairs.
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgp2AY0tJ6CDb.pgp
Description: PGP signature
On Saturday 2006-03-11 00:22 +, Ian Hickson wrote:
On Fri, 4 Nov 2005, L. David Baron wrote:
On Monday 2005-10-31 10:53 +1100, Lachlan Hunt wrote:
The current web-apps draft:
| For styling languages that consist of pure text, user agents must use
| a concatenation
On Thursday 2006-03-09 17:56 +, Ian Hickson wrote:
On Thu, 9 Mar 2006, L. David Baron wrote:
It says:
Conformance requirements phrased as requirements on elements,
attributes, methods or objects are conformance requirements on user
agents.
The ins and del elements
defined by the table following it.
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgpuyTtYjFYjx.pgp
Description: PGP signature
in HTML 4.01 that are widely implemented and are not
described in this document, should I be sending individual email
messages to this list pointing out the omissions?
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS
-work/ (which is what
the document claims the permanent URL for that version is)
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
pgp2e5TJYBi90.pgp
Description: PGP signature
a user event like a click or a
keypress that expresses the user's choice to navigate to a different
state (like navigating to a different page).
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, Mozilla Corporation
elements after the fact.
It was defined in CSS1 to apply to links and then broadened in scope in
CSS2.
You're thinking of :active.
:hover was not in CSS1 at all, and no specification that I know of
limited it to links.
-David
--
L. David BaronURL: http
.
-David
--
L. David BaronURL: http://dbaron.org/
Technical Lead, Layout CSS, The Mozilla Foundation
pgpye2wgfMVRX.pgp
Description: PGP signature
93 matches
Mail list logo
