/show_bug.cgi?id=1421938
Standard:
https://drafts.csswg.org/css-content-3/#quotes (not yet updated to reflect
recent WG resolution)
Updated spec, and requested publication so hopefully should hit
http://www.w3.org/TR/css-content-3/ later this week.
~fantasai
for
compatibility.
Since I just ran across this thread, current status of the spec is a lot better:
https://lists.w3.org/Archives/Public/www-style/2019Apr/0024.html
~fantasai
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org
/css-scroll-snap-1/#scroll-margin
Also, feel free to complain at me if anything in the spec is unclear. :)
https://github.com/w3c/csswg-drafts/issues
IRC: fantasai
Bugzilla: fantasai.b...@inkedblade.net
~fantasai
On 3/8/19 4:51 PM, Hiroyuki Ikezoe wrote:
Summary:
The scroll snap specification
ssment. There are parts
of Selectors 4 that are a little shaky, but this is so closely analogous
to an existing feature that it doesn't seem like one of them.
~fantasai
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/li
an unprefixed implementation of any
CR-level feature they can demonstrate to be correctly implemented
according to spec, and should avoid exposing a prefixed variant
of that feature.” -- https://www.w3.org/TR/CSS/#testing
Media Queries Level 4 is in CR, so anything there is good to go.
~fantasai
ensus?
Yes, the spec reflects general consensus, and has been explicitly cleared
for shipping by the CSSWG (as of several years). See issue at the bottom
of the intro:
https://www.w3.org/TR/css-logical-1/#intro
~fantasai
___
dev-platform mailing list
On 10/04/2018 04:26 PM, Steve Fink wrote:
On 10/04/2018 03:45 PM, fantasai wrote:
Start here, at Mozilla's home page:
https://www.mozilla.org/
Give me steps to reproduce to find instructions for filing
a bug against Firefox. Ditto for up-to-date instructions
for building the source
here already. Walk me through the process of
discovering how I can contribute to Mozilla and make the
world a better place. I wouldn't be here if I hadn't
already walked that path 19 years ago, but I can't find it
anymore so I need some help.)
~fantasai
the edit to remove the issue for like tomorrow or something if
that makes things easier. :)
~fantasai
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
quot; feature was
dropped from the draft spec.
The spec is in CR, which in the CSSWG represents a consensus that the draft
is design-complete and vendors are encouraged to ship in public releases.
https://www.w3.org/TR/mediaqueries-4/
https://www.w3.org/TR/CSS/#unstab
the CSSWG typically
invites all its members to review the charter prior to proposing
it to the AC, afaict this has not happened for the SVG charter [1].
[1]
https://www.w3.org/Search/Mail/Public/search?type-index=www-svg=t=charter
~fantasai
___
dev
this being resolved, but it's clearly not updated)
~fantasai
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ron raised a number of significant issues about mask types
~fantasai
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
needs to fit into the rhythm, not necessarily
each line of it; headings usually have large margins, but the text is set
closely between lines. Similar concerns apply to blockquotes with smaller
text, figures with captions, and other block-level interruptions to prose.
~fa
is convenient. :) The formula is summarized by Simon
Sapin here:
https://twitter.com/SimonSapin/status/658219116797427712
and more detailed instructions are in the flex workshop page.
If you do, please send any feedback back to the spec editors,
e.g. to www-st...@w3.org for CSS.
Happy coding~
~fantasai
~?
https://drafts.csswg.org/selectors-4/#drag-pseudos
6. Ditto :user-error
https://drafts.csswg.org/selectors-4/#user-pseudos
7. Any other comments?
Thanks~
~fantasai
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https
for this purpose,
but, really, a genuinely useful comment in any format would help.
We comment our functions to say what they're supposed to do, but
for some reason we don't think it's necessary to do this for tests.
Non-trivial tests should have a comment stating their raison d'être.
~fantasai
their own UI. In
Firefox this could manifest itself by the spinner that replaces the
favicon when loading a tab.
Is there a reason we shouldn't expose a hook for this?
Not having any context, I don't actually understand what you're requesting.
Can you give an example, maybe?
~fantasai
contributions,
or to clarify that your contributions are in fact covered, copy-paste his legal
text, and put it in a comment in bug 1073556.
https://bugzilla.mozilla.org/show_bug.cgi?id=1073556
Easy peasy. Just don't forget to uncheck the CC box. :)
Follow-ups to m.legal.
~fantasai
://dvcs.w3.org/hg/FXTF/raw-file/tip/masking/index.html
~fantasai
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
20 matches
Mail list logo
