Brian M. Blakely, 2013-09-21 02:03 (Europe/Helsinki):
I was contemplating whether to propose a new input type, or an
attribute valid only for checkboxes. But it isn't a checkbox, so I
went with a new type value. You can choose to slide the switch or
click it in most OS implementations, so even
Realistically speaking, I don't think this will help much at all. Few
websites like using the default styling for form controls anyway and
so people would be just as unhappy with the default switch rendering
as they are with the default checkbox rendering.
The real fix is to allow styling
* Bruno Racineux wrote:
Maybe Google should announce they'll start penalizing sites who do not
gzip, to change that. Either a press release on April 1st, just as an
educational scare tactic. Or a actual Webmaster Tools notification for
more awareness of non-gzipped site, or both :)
Google have
SVG 1.1 Second Edition deprecated .getSVGDocument(), and made it an alias
for .contentDocument essentially yes.
SVG2 has not yet seen any edits related to this method. But it's not
unlikely that SVG2 will drop it given that SVG 1.1 states: This interface
is deprecated and may be dropped from
On Tue, Nov 19, 2013 at 10:31 AM, Erik Dahlström e...@opera.com wrote:
SVG2 has not yet seen any edits related to this method. But it's not
unlikely that SVG2 will drop it given that SVG 1.1 states: This interface
is deprecated and may be dropped from future versions of the SVG
specification.
Rik Cabanier, 2013-09-18 00:32 (Europe/Helsinki):
You are speaking as a developer, not as a user of a web application.
Browser could offer a 'debug' more where they break on bad calls or output
messages to the console.
Once it's 'released', the runtime should be permissive.
I somewhat agree.
On 12/11/2013 16:10 , Anselm Hannemann wrote:
If you ask me I would like to have a link on bottom of every message
to the archived version but at w3c they said it wouldn’t be possible
because this needs massive changes in the software.
More generally, IIRC the policy with W3C mailing lists is
Am 19.11.2013 08:49 schrieb Yoav Weiss:
If you'd like to further discuss that concern, can you please open up a new
thread? This one discusses solutions to the responsive images problem
use-cases (e.g. src-N, picture, srcset, etc)
My personal conclusion of this part of the thread is: The
On Tue, Nov 19, 2013 at 1:37 AM, Jonas Sicking jo...@sicking.cc wrote:
Realistically speaking, I don't think this will help much at all. Few
websites like using the default styling for form controls anyway and
so people would be just as unhappy with the default switch rendering
as they are
* Anselm Hannemann wrote:
In the mails from w3c there is a header tag with the reference to the
archived version but I couldn’t find one here.
Some http://wiki.list.org/display/DEV/Stable+URLs are trying to add such
a feature to mailman, which this list uses, but so far there is nothing
easily
On 19/11/13 01:55, Kornel Lesiński wrote:
On Tue, 19 Nov 2013 01:12:12 -, Tab Atkins Jr. jackalm...@gmail.com
wrote:
AFAIK it makes it as easy to implement and as safe to use as src-N.
Simon, who initially raised concerns about use of source in picture
found that solution acceptable[2].
On Tue, Oct 29, 2013 at 3:43 PM, Jonas Sicking jo...@sicking.cc wrote:
Strings certainly solves the use cases since anything can be encoded
into a string. However it seems to me that using structured clones
will make things a lot easier for pages in many cases. This was always
*the* top
On Tue, Oct 29, 2013 at 3:47 PM, Jasper St. Pierre
jstpie...@mecheye.net wrote:
On Tue, Oct 29, 2013 at 11:26 AM, Anne van Kesteren ann...@annevk.nl
wrote:
We currently do not have a way to have events out-of-band for the web.
What about providing a URL that the user-agent will open? If the
On Tue, Oct 29, 2013 at 3:51 PM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Oct 29, 2013 at 8:26 AM, Anne van Kesteren ann...@annevk.nl wrote:
That seems like an implementation detail. Activation could mean
dismissal, but e.g. on Mac OS X activation does not mean dismissal.
It's up to the
From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-
I agree that the look and feel is different from checkbox but all the
differences seem to be purely presentational. If you disagree, you need to
elaborate a bit more.
Interestingly, Microsoft's Windows Store apps guidelines disagree. I
On Mon, Nov 18, 2013 at 2:08 PM, Andrew Wilson atwil...@google.com wrote:
I think having them return the empty string would be fine (and would,
coincidentally, match our current implementation in Chrome).
Okay.
My one concern is that according to the current spec, is a valid |tag|
and so
On Tue, Nov 19, 2013 at 2:25 PM, Domenic Denicola
dome...@domenicdenicola.com wrote:
Use a toggle switch for binary settings when changes become effective
immediately after the user changes them.
Use a checkbox when the user has to perform extra steps for changes to be
effective.
On the
There is certainly a semantic difference between switches and checkboxes. As
much of a difference as between buttons and links.
A checkbox is part of a checklist, something you use to indicate or track the
states of things. You put a series of checkmarks on a form, then bring it to
the
2013-11-19 16:25, Domenic Denicola wrote:
From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-
I agree that the look and feel is different from checkbox but all
the differences seem to be purely presentational. If you disagree,
you need to elaborate a bit more.
Interestingly, Microsoft's
Am 19.11.2013 12:13 schrieb Markus Ernst:
Am 19.11.2013 08:49 schrieb Yoav Weiss:
If you'd like to further discuss that concern, can you please open up
a new
thread? This one discusses solutions to the responsive images problem
use-cases (e.g. src-N, picture, srcset, etc)
My personal
On Tue, 19 Nov 2013, Markus Ernst wrote:
I can't recall the reasons why Florian's proposal of combining picture
and @srcset fell out of the discussion. To me it still looks like the
most useable draft so far.
I responsed to proposals along those lines last year:
On 19 November 2013 19.13.44, Jukka K. Korpela wrote:
From the usability and accessibility point of view, this seems to
address an important issue. Authors sometimes use checkboxes (or radio
buttons) so that changing their state has an immediate effect, even
submitting a form. This may violate
On Nov 19, 2013, at 1:37 AM, Jonas Sicking jo...@sicking.cc wrote:
Realistically speaking, I don't think this will help much at all. Few
websites like using the default styling for form controls anyway and
so people would be just as unhappy with the default switch rendering
as they are with
On Tue, Nov 19, 2013 at 2:28 AM, Bruno Racineux br...@hexanet.net wrote:
If I can give two top of my head analogies. With that pattern of thinking,
something like the rather complex to understand CSS flexbox wouldn't
exist. Or inline javacript would be allowed for fear of a dumb mistake by
an
2013-11-19 22:27, Qebui Nehebkau wrote:
A checkbox represents an input with
binary state. As I understand it, whether the input is immediate or
takes effect only on some kind of submission is defined by context -
specifically, whether the checkbox is associated with a form with a
submit button.
On Tue, Nov 19, 2013 at 9:28 PM, Jukka K. Korpela jkorp...@cs.tut.fi wrote:
It would be too restrictive to require that, and an reality, things don’t
work that way. For example, if the action consists of deleting something,
you just can’t repeat it next.
Well, you can. Deletion is idempotent -
On Tue, Nov 19, 2013 at 2:07 PM, Simon Pieters sim...@opera.com wrote:
So:
picture
source ...
source ...
img src=fallback alt=...
/picture
The selection algorithm would only consider source elements that are
previous siblings of the img if the parent is a picture element, and
would
Hi
I was at the Paris RICG meetup in Paris, I understand the complexity of the
responsive requirements.
I'd like to propose the following pseudocode, building upon CSS4 range
media queries.
@media (3dppx resolution = 2dppx), (min-width: 320px) {
.artdirection {
background-image:url(high.png);
On Tue, Nov 19, 2013 at 5:37 AM, Anne van Kesteren ann...@annevk.nl wrote:
This may be part of just further defining the steps for the click
pathway in the spec, but at least in FirefoxOS right now, the
notification onclick pathway does not bring the app to the visible
front in all cases. The
On Tue, Nov 19, 2013 at 2:22 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Using a url/size pair in src=''
would be invalid if sizes='' wasn't specified.
On second thought, this isn't necessary. You can always set img
width, or just let it take the default intrinsic width of 300px.
picture
[sorry for the repeated emails]
On Tue, Nov 19, 2013 at 5:47 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Tue, Nov 19, 2013 at 2:22 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Using a url/size pair in src=''
would be invalid if sizes='' wasn't specified.
On second thought, this isn't
On 11/19/13 12:12 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 19 Nov 2013, Markus Ernst wrote:
I can't recall the reasons why Florian's proposal of combining
picture
and @srcset fell out of the discussion. To me it still looks like the
most useable draft so far.
I responsed to proposals
On Nov 19, 2013, at 4:17 PM, Laurent Perez l.lauren...@gmail.com wrote:
Hi
I was at the Paris RICG meetup in Paris, I understand the complexity of the
responsive requirements.
I'd like to propose the following pseudocode, building upon CSS4 range
media queries.
@media (3dppx
On 11/19/13 4:17 PM, Laurent Perez l.lauren...@gmail.com wrote:
I'd like to propose the following pseudocode, building upon CSS4 range
media queries.
@media (3dppx resolution = 2dppx), (min-width: 320px) {
.artdirection {
background-image:url(high.png);
background-position: center;
34 matches
Mail list logo
