ndards forum, and using that process to seek positive
consensus on its proposals prior to deciding to ship, would be better than the
circumvention of the standardization processes *and spirit* being demonstrated
here, I would think.
~fantasai
he
GitHub repository at
https://github.com/w3c/csswg-drafts/issues
For the CSS WG,
~fantasai
lmgren, David Baron, and Emilio Cobos Álvarez)
for their detailed feedback this round.
Please review the draft, and send any comments to the www-style mailing list,
, prefixed with [css-lists-3] (as I did on this message) or
(preferably) file them in the GitHub repository at
https://github.com/w3c/csswg-drafts/issues
For the CSS WG,
~fantasai
On 11/21/18 2:33 PM, Andrew Fedoniouk wrote:
:blank is quite bad as a state name
For example shall be considered as not :blank as it has initial value
deliberately set to blank string (empty string allowed).
This would match :blank.
~fantasai
https://github.com/w3c/csswg-drafts/issues/2263
Please review the draft, and send any comments to the CSSWG mailing list,
, prefixed with [selectors-4] (as I did on this
message) or (preferably) file them in the GitHub repository at
https://github.com/w3c/csswg-drafts/issues
For the CSS WG,
~fantasai
www-style list,
, prefixed with [css-display] (as I did on this
message) or (preferably) file them in the GitHub repository at
https://github.com/w3c/csswg-drafts/issues
For the CSS WG,
~fantasai
On 12/25/2017 02:54 AM, fantasai wrote:
The CSS WG has published an updated Candidate Recommendation of the
CSS Scroll Snapping Module Level 1:
https://www.w3.org/TR/css-scroll-snap-1/
This module contains features to control panning and scrolling behavior
with “snap positions”.
This
csswg-drafts/issues/1771
It's tagged against Level 4, but we did just add handling for
and .
~fantasai
Forwarded Message
https://lists.w3.org/Archives/Public/www-style/2018Mar/0001.html
The CSS WG has published an updated Working Draft of the
CSS Intrinsic and Extrinsic Siz
] (as I did on
this message) or (preferably) file them in the CSSWG GitHub repository at
https://github.com/w3c/csswg-drafts/issues
We're hoping to address the remaining issues and issue a CR in the upcoming
months (but likely not before April).
Follow-ups to www-style.
For the CSS WG,
~fantasai
snap] (as I did on this
message) or (preferably) file them in the GitHub repository at
https://github.com/w3c/csswg-drafts/issues
For the CSS WG,
~fantasai
On 02/02/2017 01:18 PM, Boris Zbarsky wrote:
On 2/1/17 6:07 PM, fantasai wrote:
Wrt this particular issue, run-ins only run into other blocks; they
do not exist in or affect layout modes other than block-and-inline.
OK, so if I have a flex container with two kids, a run-in and a block, do I
any sense.
Wrt this particular issue, run-ins only run into other blocks; they
do not exist in or affect layout modes other than block-and-inline.
~fantasai
prefixed with [css-display] (as I did on this message)
or (preferably) file them in the GitHub repository at
https://github.com/w3c/csswg-drafts/issues
For the CSS WG,
~fantasai
n 8/2/16 7:38 PM, fantasai wrote:
First one is 'display: contents':
This one is mostly a question for Mats. That said, I think this
feature adds a huge amount of complexity, and I expect that some
of its interactions with HTML are not very clearly specced. For
example,
On 06/20/2016 06:14 PM, Phillips, Addison wrote:
+I18N Core
Thanks for this. I have added this to I18N's radar [1]. Do you have a
due date for comments in mind? Or a general schedule?
Not really.
~fantasai
GitHub repository at
https://github.com/w3c/csswg-drafts/issues
For the CSS WG,
~fantasai
them to , prefixed with [css-pseudo-4]
(as I did on this message).
For the CSS WG,
~fantasai
ist, ,
and please, prefix the subject line with
[css-cascade-4]
(as I did on this message).
For the CSS WG,
~fantasai
is message).
For the CSS WG,
~fantasai
difficult to implement atm, and we can disallow at
a syntactic level if we retain only the shorthand 'display'. (The
show/hide switch, not being a longhand of 'display', will stay
separate.)
For the CSS WG,
~fantasai
request for something similar came up on the
CSSWG ML just recently:
http://lists.w3.org/Archives/Public/www-style/2014Jul/0131.html
In that case it's about retrieving the OS's notion of this color.
~fantasai
eak-point.
There's further discussion about this in
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13108
I've no comment on concerns about compatibility with XML, but I can say
that I've typed &zwsp; multiple times expecting it to work and find it
surprising that and work, but &zwsp; does not...
~fantasai
es in weird ways, but it's the
best we can do.)
However, there is one downside to this: if the has a ancestor,
the override will not work within the unless the author overrides
that rule.
Comments welcome on this issue as well.
~fantasai
line with
[css-scoping]
(as I did on this message).
For the CSS WG,
~fantasai
ailing list [1],
, and please, prefix the subject line with
[css-cascade-3]
(as I did on this message). The deadline for comments is
** 26 August 2013 **
Please let us know if you need an extension.
We would particularly appreciate review of this module from the
HTML and WebAPI communities. Thanks!
For the CSS WG,
~fantasai
can't find how to specific audio
characteristics in a media query.
I don't think such a thing exists, but you could request it
for Media Queries Level 4:
http://dev.w3.org/csswg/mediaqueries4/
You'd want to post to www-style for that, though.
~fantasai
ses
http://www.w3.org/TR/css-counter-styles-3/#simple-symbolic
We'd especially appreciate a review of these additions.
We expect the next step to be Last Call.
Please send any comments to , and please, prefix the
subject line with
[css-counter-styles]
(as I did on this message).
For the CSS WG,
~fantasai
larly appreciate a review of Chapter 4, Cascading and Inheritance.
http://www.w3.org/TR/css3-cascade/#cascade-and-inheritance
Please send any comments to this mailing list, , and
please, prefix the subject line with
[css3-cascade]
(as I did on this message).
For the CSS WG,
~fantasai
The only value of 'appearance' that actually works IIRC is 'none'.
I'm not sure I'd recommend it as a good way forward for anything
since it's not clear how other values are supposed to work.
~fantasai
On 11/16/2012 07:38 AM, frederick.hir...@nokia.com wrote:
fantasai
Is the WG response (see below) to your Last Call issue (LC-2642) [1]
on HTML Media Capture [2] regarding clarification of accept and capture
[attributes of ] sufficient for us to close the issue?
If timeless and/or hixie are
:not(:valid-drop). I'm unsure if
it's necessary to add at this point, but can add it and mark at-risk for
the time being.
~fantasai
On 08/13/2012 11:55 PM, Ryosuke Niwa wrote:
On Mon, Aug 13, 2012 at 9:19 PM, fantasai mailto:fantasai.li...@inkedblade.net>> wrote:
The CSSWG discussed drag-and-drop pseudo-classes today. The current
proposal is to have three pseudo-classes:
* One for the element repres
-drop :valid-drop
:no-drop:no-drop :invalid-drop:invalid-drop
Thanks~
~fantasai
cgi?product=CSS&component=Flexbox&resolution=---
[2] http://lists.w3.org/Archives/Public/www-style/
~fantasai
Co-Editor, CSS Flexible Box Layout
r '0035', it needs to be processed as '0035' not '35' or '35.00'.
For a number, they are all equivalent. For things like credit card numbers
and postal codes, they probably aren't.
The spec could perhaps benefit from an example of how /not/ to use
type=number here...
~fantasai
ng
a real element that is so problematic that we're considering a pseudo-
element here?
~fantasai
give me at *least* 15 minutes to respond? No? :-)
http://krijnhoetmer.nl/irc-logs/css/20120114
In the interests of moving on with this, I've changed the spec to the
above. I welcome implementation experience on whether this works. If it
doesn't, I'm happy to change it back.
Sounds okay to me.
~fantasai
The official deadline for comments is 7 February 2012. Let us know if you
need an extension so that we don't miss your comments.
Thanks~
~fantasai
on would be www-st...@w3.org,
with [mediaqueries] in the subject line.
~fantasai
wsp */; text-wrap: normal; }
pre wbr { content: none; }
I'm leaning somewhat towards the second option.
~fantasai
deal with the rendering requirements by
specifying
wbr { content: '\8203' /* zwsp */;
text-wrap: normal; }
Slightly off-topic: in CSS3, there is an 'avoid' value for 'text-wrap',
which is designed to solve problems similar to those currently dealt
with by using / combinations.
~fantasai
text-shadow. If implementers want to take that on, it can be part of CSS3
Text. Also there were proposals for a text-outline property, which would
do something similar, based on feedback from the TimedText WG.
http://www.w3.org/TR/css3-text/#text-shadow
http://www.w3.org/TR/css3-text/#text-outline
~fantasai
the element to ever match :active. And if there is behavior to
activate, it should be keyboard-activateable as well, not just mouse-
clickable.
I'm also interested to know whether there's a web-compat issue here or
just a bug-compat issue, and what the implementers think.
~fantasai
odules only, which is equivalent to
naming large features of HTML.
How do you define a "large feature of HTML"?
~fantasai
o look at for Selectors 4.
~fantasai
http://www.w3.org/TR/css3-marquee/#the-overflow-style
Having the overflow method specified separately from whether or
not the content can overflow is probably a good idea.
~fantasai
On 01/14/2010 12:49 AM, Simon Montagu wrote:
On 01/11/2010 11:35 PM, fantasai wrote:
On 11/26/2009 10:54 PM, Simon Montagu wrote:
I assume your Gecko example is using a very recent version of Gecko,
such as a nightly build or a beta of Firefox 3.6? I fixed this issue
only a few months ago
Ian Hickson wrote:
On Mon, 4 May 2009, fantasai wrote:
Section 10.2.6, i.e. The XHTML syntax: Rendering: Punctuation and decoration
contains some style rules for handling the [rules] and [frames] attributes
of the element. I haven't reviewed it all in detail but this part
table[frames
problems with that approach.
There's a collection of tests for these attributes here:
http://fantasai.inkedblade.net/markup/tests/table-frame-rules/
I should probably expand it to include tests for the empty string and junk
valuse, but that's what it is for now.
~fantasai
Ian Hickson wrote:
On Wed, 11 Feb 2009, fantasai wrote:
Given the state of current implementations and the fact that hidden input
elements do have distinct enabled and disabled states, I don't understand
the reasoning behind this change.
http://twitter.com/WHATWG/status/1198455588
The
Ian Hickson wrote in
http://lists.w3.org/Archives/Public/www-style/2009Feb/0328.html :
On Wed, 29 Oct 2008, Lachlan Hunt wrote:
fantasai wrote:
Lachlan Hunt wrote:
http://lachy.id.au/dev/css/tests/selectors/pseudo-classes/ui/
Interesting. I'm not convinced that :enabled and :dis
s won't be reading the spec.
It is quite likely that someone will assume is the "correct"
tag to use for a CSS+JS dialog box.
~fantasai
characters: in many cases certain carefully-chosen strokes are left out in
the smaller sizes in order to make it legible. Judging from information
about Meiryo, it seems more recent font technology uses vectors + hinting
to solve the same problem... but maybe it's something to keep in mind.
~fantasai
age was used as a dialog rather than part of the normal content
> flow. ...
You could use instead of . "Dialog" is an alternate spelling
of "dialogue" in common English, but IIRC "dialogue" is never used for dialog
boxes. I'm sure mpt can correct me if I'm wrong...
~fantasai
we have a similar problem.
~fantasai
a separator.
sizes=16x16+32x32+64x64
For SVG icons, you'd probably want the ability to specify a ratio instead.
(And I suppose for sound icons, you'd want the length of the sound clip...)
Also, I didn't see anything in the spec about parameters needing to be
prefixed, only subtypes. Maybe I missed it.
~fantasai
ot;whatwg.icns">
This would however effectively define an open-ended set of rel values,
and also it is dubious whether a size can be considered a relationship.
I don't think it can. This seems pretty wrong to me: the right place for
this information would be, as Jeff Walden said, in the 'type' attribute.
~fantasai
background,
you can see the relevant discussions for CSS
http://www.w3.org/blog/CSS/2007/12/12/case_sensitivity
~fantasai
them, but they don't
need to be side-by-side with the original page: in that case a
floating box in the middle of the page would be ideal. Etc.
~fantasai
s Quotation_Mark property is adequate.)
~fantasai
Nikola Mitic wrote:
fantasai wrote:
Michael wrote (on www-style):
I have a fluid layout so it changes width because of the browser window.
There is the slight problem that some of the images I use might be too wide.
So I use max-width:100% to prevent this from happening. This works great
"name" of
"a person" can also be considered the "title" of "a work".
~fantasai
Robert O'Callahan wrote:
A related question is whether display:none audio and video elements
should produce sound.
No. "display: none" is defined to affect all media, and that certainly
should not change for and .
~fantasai
the author just bothers to put
it there. Of course the author could make the print result pretty, rather
than just a text dump. There are very few cases where a separate document
would be necessary.
~fantasai
around innumerable
browser bugs and limitations. Trying to constrain their use is imho unwise.
When Tantek Çelik comes to the WHATWG or the HTMLWG and says "I want a central
registry for class names", then make one. Until then, I suggest simply leaving
this domain to the μF guys (and gals).
~fantasai
Benjamin Hawkes-Lewis wrote:
An element might kill several of these birds with one stone.
I'd rather see an element than an element.
It is more generally useful.
~fantasai
ts readability:
http://microformats.org/wiki/datetime-design-pattern
The element is much more appropriate for this than .
[1] http://code.google.com/webstats/2005-12/classes.html
~fantasai
Alexey Feldgendler wrote:
On Tue, 06 Mar 2007 02:17:43 +0100, fantasai
<[EMAIL PROTECTED]> wrote:
For printing, the element would make it easy to cut out
extraneous content and print just the main content of a web page.
It just occurred to me: because of this particular possibility
onsistent).
For printing, the element would make it easy to cut out
extraneous content and print just the main content of a web page.
~fantasai
Henri Sivonen wrote:
On Jan 10, 2007, at 11:40, fantasai wrote:
That depends, actually, on the language. Browsing the Chinese journal
section of a university East Asian Library, I noticed that the Chinese
journals didn't use normal/italics -- instead they switched the style of
font be
cts itself -- it says
must only be used to denote importance yet the contenteditable
"bold" feature will emit .
+1
~fantasai
cause all
that matters is that their presentation is the same, but that argument doesn't
hold up for non-Latin texts. Restyling sitewide to use 'text-emphasis'
instead of 'font-style: italic' would be a nifty thing on a Japanese website.
Restyling the same way would just be silly.
~fantasai
sound out ruby annotations, just
like you can't just sound out base text, because kana and bopopmofo
are not a linguist's phonetic annotation system, they're writing
systems and all that implies. :)
~fantasai
or grammatical labelling,
etc. The key difference from other annotation systems is that it can be
word-for-word without being awkward. (Imagine doing this with footnotes.)
~fantasai
ally associate the quotes with Mark Twain.
~fantasai
hive
is used, as was suggested earlier. This gives us a way to say
without implying
and without dropping the 'type' attribute entirely (which was the other
solution pointed out on the whatwg list).
~fantasai
using the title=""
attribute, that's not something a "machine" has to know about).
That's an interesting relationship. Perhaps it could be expressed as
"index feed" within the context of WA1.0's current link type definitions.
In any case, I would like to see this use case definitively addressed.
Such a link would be the most appropriate default feed to subscribe to
from an entry page, if it were somehow clearly labelled.
~fantasai
la.org/ , i.e. the homepage of the website.
[1] http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html#index
[2] http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html#top
~fantasai
fn element contains the definition for the _term_ of
the dfn element.
I'd just strike "the contents".
definition for the term given by the dfn element.
~fantasai
Ian Hickson wrote:
On Sun, 26 Nov 2006, fantasai wrote:
Ran across this comment:
http://www.whatwg.org/specs/web-apps/current-work/#features
# Should textContent be defined differently for dir="" and ?
What would it mean to define textContent differently for dir="" and
Carcassonne
Photo by Mariel
~fantasai
s kind of usage, albeit without the captions:
http://www.mozilla.org/contribute/writing/markup#notes
~fantasai
Ran across this comment:
http://www.whatwg.org/specs/web-apps/current-work/#features
# Should textContent be defined differently for dir="" and ?
What would it mean to define textContent differently for dir="" and ?
~fantasai
that is a stronger argument for keeping char than align.
Another argument for align is that CSS alone can't do anything useful
about alignment in columns, since inheritance only works through the
element tree. Of course, I'd prefer to see that fixed in CSS.
~fantasai
and in
the CSS 2.1 draft in particular?
Easy: it didn't get removed.
http://www.w3.org/TR/CSS2/tables.html#q7
~fantasai
R/html40/struct/tables.html#h-11.4.1
~fantasai
locale.
What locale?
~fantasai
;s user agents.
You could use . Just always use for the figure caption.
Actually, I think WA should generally allow the use of as a
terminal-level header, similar to the simplesect element in DocBook.
It's a useful markup construct sometimes, at least in my experience.
~fantasai
Ian Hickson wrote:
On Tue, 4 Apr 2006, fantasai wrote:
I'm wondering what WA1 considers appropriate markup for a figure with a
caption.
As Lachlan points out, putting caption text in an attribute isn't very
good design and it gets in the way of a lot of things: marking u
I'm wondering what WA1 considers appropriate markup for
a figure with a caption.
~fantasai
ups.yahoo.com/group/rng-users/message/422
Does moving the choice up higher help any?
~fantasai
Henri Sivonen wrote:
On Apr 2, 2006, at 18:56, fantasai wrote:
I'd rather see the id attribute restricted to an NCName token insofar
as possible. We can make an exception for Hixie's repetition templates,
but otherwise I think it should be compatible with the XML ID syntax.
D
n't care what characters there are, other tools do. We can't
express IDness in a schema if we insist on ignoring its syntactic
restrictions.
~fantasai
The content model for excludes form controls. Should it
also exclude links and other interactive things defined in WA1?
~fantasai
Henri Sivonen wrote:
Single select:
Is it conforming for an option to be both selected and disabled? (I
think it shouldn't be conforming.)
I agree with that.
And analogously: Is is conforming for a radio button to be both checked
and disabled if the whole set is not disabled? (This one is
Ian Hickson wrote:
On Tue, 28 Mar 2006, fantasai wrote:
Another issue is the possible use of U+2212 MINUS SIGN intead of U+002D
HYPHEN-MINUS. This last, at least, should be handled whenever the number
is parsed from the text content rather than in an attribute.
In the text, negative
ctuation or spaces as the thousands
separator.
Another issue is the possible use of U+2212 MINUS SIGN intead of U+002D
HYPHEN-MINUS. This last, at least, should be handled whenever the number
is parsed from the text content rather than in an attribute.
~fantasai
. So do most of the civil engineers I know.
As for spelling, I'm likely to use "gage" for e.g. "22-gage steel deck",
but I'm inclined to use "gauge" for "fuel gauge". But that's just me.
~fantasai
The other two definitions mention the British variant "metre", but this
one does not.
FWIW, the hits on google for gauge and gage are similar if you search
for the words alone, but in conjunction with things like "fuel" or "steel"
or "measure", gauge comes out about an order of magnitude more popular.
~fantasai
on ...
The "order of magnitude increase in complexity" due to multiple elements
strikes me as accurate, though.
Just as a note on presentation requirements for CSS or XBL or whatever:
this thing needs to handle graphical 3.5/5 stars and things like that.
~fantasai
1 - 100 of 104 matches
Mail list logo
