Am 20.11.2013 06:24 schrieb Bruno Racineux:
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
Am 20.11.2013 22:27 schrieb Tab Atkins Jr.:
On Wed, Nov 20, 2013 at 9:25 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Simon Pieters wrote up Kornel's earlier approach to a saner, more
palatable source selection algorithm for picture (rather than
copying video/audio). This approach also has a
Something that just came to my mind: Unlike srcset and src-N, picture
has the power to support MQs beyond viewport width:
picture
source media=screen src=...
source media=print src=...
img src=...
/picture
The UA will have to download both sources, or printing will be delayed.
Is this a
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
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
Am 13.11.2013 14:52 schrieb John Mellor:
style
@media (max-width: 19.99em) {
.artdirected { content: replaced image-set(128px; attr(srcs-smallicon));
}
}
@media (min-width: 20em) {
.artdirected { content: replaced image-set(100% (30em) 50% (50em) 33%;
attr(srcs-flexwidth)); }
}
/style
Am 12.11.2013 14:33 schrieb Ryosuke Niwa:
On Nov 12, 2013, at 4:11 PM, Adam Barth w...@adambarth.com wrote:
On Tue, Nov 12, 2013 at 12:08 AM, Jukka K. Korpela jkorp...@cs.tut.fi wrote:
2013-11-12 9:58, Adam Barth wrote:
Unfortunately, we can't add new tags to head. If the parser sees a
tag
Am 12.11.2013 17:48 schrieb Markus Lanthaler:
On Tuesday, November 12, 2013 5:04 PM, Markus Ernst wrote:
We could define some ways to list set of images that could be
replaced for a given img element in HTML and then let CSS pick which
one to use for example.
style type=text/css
@media (min
Am 12.11.2013 18:50 schrieb Adam Barth:
We might even be able to make this work without inventing anything:
style type=text/css
@media (min-width: 480px) {
.artdirected {
width: 30px;
height: 30px;
background-image: image-set(url(small.png) 1x, url(small-hires.png) 2x);
}
}
Am 10.11.2013 19:48 schrieb Jukka K. Korpela:
2013-11-10 19:36, Markus Ernst wrote:
Having a look at the proposal, and reading the thread especially with
regard to complexity and verbosity, I got the impression that @src-n
shares a main objection with @srcset and picture, that it mixes up
Am 10.11.2013 18:53 schrieb Tab Atkins Jr.:
This proposal does not address Variable-Sized Images; handling the
difficulty and verbosity of that is indeed centralized to the
situations element, but that doesn't make it much better.
I omitted variable-sized images indeed. The syntax you propose
Am 10.11.2013 18:36 schrieb Markus Ernst:
Moving the distinction of viewing situations to the head would have some
advantages IMO:
- Verbosity is centralized, thus has not to be repeated in every img
element
- The UA does not need to evaluate the same MQs again for every img in
the content
Am 10.04.2013 21:14 schrieb Wesley Johnston:
Finally, apps can already solve this problem today - they know when they go into the
background (for different permutations of background, as Jer mentioned), and
they can pretty trivially mute or pause their playing audio. Most of them don't.
Am 21.03.2013 12:10 schrieb James Ross:
Just as an added data-point (that I only noticed today) - Windows 7's
placeholder implementation in the Start menu and Explorer's search box:
- Focusing the input box with tab/Control-E or autofocus when opening the
Start menu does *not* hide the
Am 20.03.2013 02:20 schrieb Kit Grose:
In almost every case the placeholder remains visible until the user has begun
typing, as I strongly believe it ought to be remain in the specification, since
it provides the contextual hint for as long as possible.
Do you refer to author implementations
...
Best Regards
Markus Ernst
Am 18.03.2013 13:27 schrieb Boris Zbarsky:
On 3/18/13 5:31 AM, Markus Ernst wrote:
- Opera and Safari hide it when the field gets focus
The behavior of Safari here is platform-dependent or possibly
version-dependent. Safari 6 on Mac doesn't hide the placeholder until
you start typing
Am 15.01.2013 00:39 schrieb Nasko Oskov:
Hi whatwg,
I recently became aware of the proposal to add AllowSeamless attribute that
will permit cross-origin seamless iframes (
http://wiki.whatwg.org/wiki/AllowSeamless). We are currently working on a
new security policy in Chrome, which will separate
Am 18.01.2013 14:40 schrieb Anne van Kesteren:
On Tue, Jan 15, 2013 at 2:44 PM, Markus Ernst derer...@gmx.ch wrote:
The allow-seamless mechanism is to be triggered at the side of the embedded
resource, which would also be the one affected by possible security risks
(if I get this right
Am 15.01.2013 01:36 schrieb Nasko Oskov:
On Mon, Jan 14, 2013 at 3:48 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jan 15, 2013 at 12:39 AM, Nasko Oskov na...@chromium.org wrote:
Based on the existing security concerns listed in the proposal and the
fact
that it might prevent a
Am 28.12.2012 03:04 schrieb Ian Hickson:
I've added a feature to HTML to enable users (and authors) to sort tables.
The basic design of the feature is that if a column's th has a sorted=
attribute, the UA will sort the table every time the mutation observers
would fire (before they fire). A
Am 05.12.2012 10:45 schrieb Jonas Sicking:
I hear no end of people arguing that HTTP headers are too hard for
people to use. Could we make these settable through meta elements as
well as, or instead of, using headers.
I am one of those authors with limited technical background. IMHO the
Am 22.11.2012 01:51 schrieb Ian Hickson:
On Sun, 14 Aug 2011, Timo Beermann wrote:
It should be able to implemet checkboxes, where by only
activating/deactivating this single checkbox you can active/deactivate
multiple other checkboxes. That is possible with scripting today, but it
should be
Am 07.11.2012 15:48 schrieb Jukka K. Korpela:
I suppose that the heuristics would include recognizing a div element
to which class main has been assigned. Then one could argue that
main is not needed, as authors can keep using div class=main, as
millions of pages use.
I doubt that this is
Am 10.10.2012 20:36 schrieb Ian Hickson:
On Wed, 10 Oct 2012, Tim Kadlec wrote:
That's actually exactly why it's better _not_ to plan for it. We can't
design features for problems we don't understand. It's better to wait
until we have real problems before fixing them.
You may not be able to
Am 11.10.2012 18:36 schrieb Ian Hickson:
On Thu, 11 Oct 2012, Markus Ernst wrote:
IMHO as an author, the bandwidth use case is not solved in a future
proof manner
It's not solved at all. I didn't attempt to solve it. Before we can solve
it, we need to figure out how to do so, as discussed
Am 07.09.2012 03:36 schrieb Tab Atkins Jr.:
This email is an extension of the thread started at
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-August/036953.html
by John Mellor, distilling the core problem he has into a more
easily-understood and digested form.
The srcset attribute,
Am 13.08.2012 18:39 schrieb Henri Sivonen:
Ignoring implementation issues for a moment, I think it would be
conceptually easier it to disentangle these axes like this:
Non-art directed:
img src=1xsampling.jpg hisrc=2xsampling.jpg alt=Text alternative
Art directed:
picture
source
Am 10.08.2012 12:06 schrieb Odin Hørthe Omdal:
On Thu, 09 Aug 2012 18:54:10 +0200, Kornel Lesiński
kor...@geekhood.net wrote:
One stylesheet can be easily reused for pixel-perfect 1x/2x layout,
but pixel-perfect 1.5x requires its own sizes incompatible with 1x/2x.
Apart from it possibly
Am 07.08.2012 21:09 schrieb Ian Hickson:
On Tue, 22 May 2012, Markus Ernst wrote:
Am 18.05.2012 23:19 schrieb Kornel Lesiński:
If you'd like to see picture proposal succeed, then please help
fixing its drawbacks. Make selection and embedding of 2x images
easier. Give UA freedom to use cached
Am 11.07.2012 00:59 schrieb Ian Hickson:
On Fri, 4 May 2012, Tab Atkins Jr. wrote:
On Wed, May 2, 2012 at 3:57 PM, Ian Hicksoni...@hixie.ch wrote:
On Wed, 6 Apr 2011, Tab Atkins Jr. wrote:
An app may dynamically set inputs or groups of inputs to readonly
based on app state. When you submit,
Am 06.06.2012 14:36 schrieb Henri Sivonen:
On Wed, May 23, 2012 at 6:21 PM, Florian Rivoalflori...@opera.com wrote:
1) simplyfy srcset to only accept the *x qualifier
Is there a good reason to believe that * will be something other than
a power of two?
That is, could we just optimize the *x
Am 27.05.2012 02:16 schrieb Adam Barth:
Hi whatwg,
I've added a proposal to the wiki
http://wiki.whatwg.org/wiki/AllowSeamless about letting a document
indicate that it is willing to be displayed seamlessly with a
cross-origin parent. This proposal is a refinement of the approach
previously
Am 27.05.2012 12:00 schrieb Markus Ernst:
allowseemles=example.org *.example.org shop.otherdomain.com,
inherit-style
It seams I made a typo here.
Am 27.05.2012 12:19 schrieb Adam Barth:
On Sun, May 27, 2012 at 3:00 AM, Markus Ernstderer...@gmx.ch wrote:
Am 27.05.2012 02:16 schrieb Adam Barth:
I've added a proposal to the wiki
http://wiki.whatwg.org/wiki/AllowSeamlessabout letting a document
indicate that it is willing to be
Am 24.05.2012 10:27 schrieb Matthew Wilcox:
Excellent, sorry I was not clear on that; this is looking good!
I would like to re-iterate that this solution is another which puts
design properties into mark-up directly, and just like oldpicture
and srcset, this means that when it's time to
Am 24.05.2012 11:13 schrieb Matthew Wilcox:
I agree, the problem is that... it's still a problem. It's not always
a cropped version, it's sometimes a different image entirely - but we
can only sense the viewport rather than the space into which an image
is sitting. Because we can only sense the
Am 23.05.2012 17:21 schrieb Florian Rivoal:
Here's what I think we should do:
1) simplyfy srcset to only accept the *x qualifier
2) add support for srcset as an attribute of the source sub-element of
the picture element (in addition to src, or instead of it? I am not
sure).
Then you could do
Am 21.05.2012 07:49 schrieb Mike Gossmann:
img src=/img/people.jpg sizes=100x200 300x250 900x300
pattern=/tools/resizer.php?img=people.jpgamp;width={w}amp;height={h} alt=A picture of some
people.
I am somehow surprised that there are no reactions to this proposal. To
me as a humble author
Am 22.05.2012 12:46 schrieb Andy Davies:
On 22 May 2012 10:43, Anne van Kesterenann...@annevk.nl wrote:
On Tue, May 22, 2012 at 10:21 AM, Markus Ernstderer...@gmx.ch wrote:
I am somehow surprised that there are no reactions to this proposal. To me
as a humble author it looks like it would
Am 18.05.2012 23:19 schrieb Kornel Lesiński:
If you'd like to see picture proposal succeed, then please help fixing
its drawbacks. Make selection and embedding of 2x images easier. Give UA
freedom to use cached higher-quality images when it can. Give UA freedom
to choose images to minimize
Am 21.05.2012 07:49 schrieb Mike Gossmann:
When all the picture vs srcset started showing up on twitter, I was initially
behind picture. I'm sure you all know the arguments for it, and I liked those
arguments. Today though, I was reading an article about the two, and there was
a
Am 17.05.2012 19:48 schrieb Tab Atkins Jr.:
On Thu, May 17, 2012 at 10:27 AM, Jeremy Keithjer...@adactio.com wrote:
Tab wrote:
Absolutely agreed. Like several others have suggested, I think we
should just go with a min-width:100px approach, which is much
clearer. It also lets us add
Am 15.05.2012 09:28 schrieb Ian Hickson:
img src=face-600-...@1.jpeg alt=
srcset=face-600-...@1.jpeg 600w 200h 1x,
face-600-...@2.jpeg 600w 200h 2x,
face-icon.png 200w 200h
Re-reading most parts of the last day's discussions, 2 questions
Am 18.05.2012 13:09 schrieb James Graham:
On 05/18/2012 12:16 PM, Markus Ernst wrote:
2. Have there been thoughts on the scriptability of @srcset? While
sources can be added to resp. removed from picture easily with
standard DOM methods, it looks to me like this would require complex
string
Hello
I try to follow the actual discussion with much interest and, I admit,
not full understanding. If my inputs are inappropriate, please feel free
to ignore this message.
I read the current spec and huge parts of today's discussions to find
out how images with multiple sources are
Am 03.05.2012 00:50 schrieb Ian Hickson:
On Mon, 7 Mar 2011, Markus Ernst wrote:
A content management or blog system for a corporate website allows to
set font and background colors. The designers define allowed color sets
the way that the corporate design guidelines are respected
I apologize in case this has been discussed before - the list archive
search seems to be broken right now, as it does not find any matches
when searching for color.
I just noticed a note in the spec of input type=color
Am 12.04.2012 22:35 schrieb Ojan Vafai:
On Thu, Apr 12, 2012 at 1:32 PM, Adam Barthw...@adambarth.com wrote:
On Thu, Apr 12, 2012 at 1:17 PM, Ojan Vafaio...@chromium.org wrote:
On Thu, Apr 12, 2012 at 1:07 PM, Boris Zbarskybzbar...@mit.edu wrote:
On 4/12/12 3:49 PM, Adam Barth wrote:
The
Am 05.04.2012 03:59 schrieb Ojan Vafai:
On Wed, Apr 4, 2012 at 6:52 PM, Ojan Vafaio...@chromium.org wrote:
1. We should add iframe[seamless] { display:block; }.
http://www.whatwg.org/specs/web-apps/current-work/#embedded-content-2 already
expects iframe:not([seamless]) { border: 2px inset;
Am 25.01.2012 16:39 schrieb Matthew Wilcox:
It's also worth noting another use case for this being in mark-up and not
just server-negotiated rescaling of a single image:
Imagine a profile photo on an About page. At large sizes you want to use a
full body shot, at smaller sizes you need to
Am 25.01.2012 15:07 schrieb Matthew Wilcox:
In fact, please just read the blog post Bruce Lawson (Opera Software)
made summarising the last few months of effort on this, and his proposal
for a mark-up level solution (which I'm in broad support of, though there
are a lot of knotty issues with any
Am 21.01.2012 15:19 schrieb Cameron Heavon-Jones:
On 20/01/2012, at 6:58 PM, Bronislav Klučka wrote:
Hello
There are two recent threads on localisation of form fields, one on input
type=date, the other on the Decimal comma in numeric input. Both are about the
question whether the form
Hello
There are two recent threads on localisation of form fields, one on
input type=date, the other on the Decimal comma in numeric input. Both
are about the question whether the form field value should be displayed
according to the element's language, or rather based on the user's
Hello
Viewing the logs of applications I wrote, I noticed that a considerable
number of requests are from robots following links of types such as Add
to shopping cart or Remember this item - links that typically point
to the same page they are clicked on, with some GET variable that
triggers
Am 21.06.2011 02:16 schrieb Ojan Vafai:
It is certainly the case that some large subset of users use spaces to align
content, not to mention really care about things like two spaces after
periods, etc. One way or another, contentEditable needs to support this.
If we were starting with a clean
Am 14.06.2011 18:06 schrieb Tab Atkins Jr.:
On Tue, Jun 14, 2011 at 2:04 AM, Markus Ernstderer...@gmx.ch wrote:
Am 14.06.2011 09:32 schrieb Ian Hickson:
On Fri, 11 Mar 2011, Markus Ernst wrote:
Consider this markup of Andy's use case:
pI always like to eat these cheeses:
il
iliCheddar/ili
Am 14.06.2011 09:32 schrieb Ian Hickson:
On Fri, 11 Mar 2011, Markus Ernst wrote:
Instead of a new paragraph concept, there could also be a new concept
for inline (resp. Phrasing Content) lists. The concept is actually not
too new - for quotes, e.g., we've had both block levelblockquote
While following the discussions about Aryeh Gregor's great work on
execCommand(), I get the impression that this method is very limited to
some basic formatting actions. It provides shortcuts for a limited set
of DOM actions, but is not really extendable or generalizable.
Some of the
Am 19.05.2011 20:39 schrieb Aryeh Gregor:
On Tue, May 17, 2011 at 4:09 AM, Markus Ernstderer...@gmx.ch wrote:
While discussing about contenteditable elements, the WYSIWYG aspect was
mentioned. For real WYSIWYG in a text editor of a CMS, Blog, Forum or
whatever, it would be necessary for the
Am 17.05.2011 22:28 schrieb Ryosuke Niwa:
On Tue, May 17, 2011 at 12:50 PM, Aryeh Gregorsimetrical+...@gmail.comwrote:
On Tue, May 17, 2011 at 3:19 AM, Ryosuke Niwarn...@webkit.org wrote:
I completely disagree. As a user, I want semantics when I write my blog
entry on WordPress so that I
Am 16.05.2011 21:20 schrieb Aryeh Gregor:
On Mon, May 16, 2011 at 9:33 AM, Markus Ernstderer...@gmx.ch wrote:
I have seen content management systems where text editors tweak the enter
key to behave the same also in non-IE UAs (e.g. if you use Contenido with
TinyMCE, Firefox produces the same
Am 13.05.2011 12:00 schrieb Michael A. Puls II:
On Thu, 12 May 2011 16:28:47 -0400, Aryeh Gregor
simetrical+...@gmail.com wrote:
Another problem with p is that it's very easy to create
unserializable DOMs with it. I've seen cases where at least some
browsers will put things inside p that will
Hello
While discussing about contenteditable elements, the WYSIWYG aspect was
mentioned. For real WYSIWYG in a text editor of a CMS, Blog, Forum or
whatever, it would be necessary for the contents of the contenteditable
element to:
- Disable the styles of the surrounding page
- Enable the
Am 12.05.2011 22:28 schrieb Aryeh Gregor:
Behavior for Enter in contenteditable in current browsers seems to be
as follows:
* IE9 wraps all lines inp (including if you start typing in an
empty text box). If you hit Enter multiple times, it inserts empty
ps. Shift-Enter insertsbr.
This is
Am 16.05.2011 15:33 schrieb Markus Ernst:
Am 12.05.2011 22:28 schrieb Aryeh Gregor:
A problem withp is that it has top and bottom margins by default,
so hitting Enter once will look like a double line break. One
real-world execCommand() user I looked at (vBulletin) sets p { margin:
0 } for its
Am 15.03.2011 17:36 schrieb Christoph Päper:
Jukka K. Korpela:
Christoph Päper wrote:
input type=number id=fontsize value=12 unit=pt
Or do you mean that the presence of the unit=... attribute would trigger a
special implementation of numeric input, so that the user is expected to enter
Am 13.03.2011 21:46 schrieb Aryeh Gregor:
2) How much work should we go to to produce nice-looking markup?
E.g., if the user unbolds baz in
div style=font-weight:bold
pFoo
pBar baz
/div
should we produce something like
div
p style=font-weight: boldFoo
pbBar/bbaz
/div
like WebKit does, or
Am 10.03.2011 19:18 schrieb Jukka K. Korpela:
Markus Ernst wrote:
Would it cause serious issues to add the Phrasing Content category to
these three elements [ol, ul, dl] thus allowing them inside the p
element?
I'm afraid it would, and I think that's the reason why the content model
hasn't
Am 10.03.2011 17:58 schrieb Andy Mabbett:
On 10 March 2011 08:20, Jukka K. Korpelajkorp...@cs.tut.fi wrote:
what should we say to people to need to use paragraphs
that contain lists, for example?
This has concerned me for some time.
Consider a more complex scenario:
pI always like to eat
Am 09.03.2011 06:51 schrieb Jukka K. Korpela:
Jonas Sicking wrote:
I'm having a little bit hard of a time figuring out what a good UI
would look like in the general case. I.e. what should the UI look like
for
input type=date id=date name=date
value=2011-04-01 list=datelist exclusive
datalist
Am 09.03.2011 12:19 schrieb Diogo Resende:
On Tue, 8 Mar 2011 16:51:25 -0800, Jonas Sicking wrote:
On Tue, Mar 8, 2011 at 10:46 AM, Markus Ernst derer...@gmx.ch wrote:
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi wrote
Am 07.03.2011 18:27 schrieb Markus Ernst:
Reading 4.10.7.1.15 on the Color state of the input element, I miss a
possibility how to define a set of allowed colors. For other states of
the input element there are such possibilities, such as setting min, max
and step attributes for input type=date
In 4.10.12 on the Option element, the spec states:
The label attribute provides a label for element. The label of an option
element is the value of the label attribute, if there is one, or the
textContent of the element, if there isn't.
The value attribute provides a value for element. The
Am 08.03.2011 15:22 schrieb Jukka K. Korpela:
Markus Ernst wrote:
select
option label=Label1TextContent1/option
option label=Label2TextContent2/option
/select
- IE 8, Opera 11 and Chrome 9 display Label1 and Label2
- Firefox 3.6 displays TextContent1 and TextContent2
Firefox's behavour seems
Am 08.03.2011 19:02 schrieb Anne van Kesteren:
On Tue, 08 Mar 2011 12:26:56 +0100, Jukka K. Korpela
jkorp...@cs.tut.fi wrote:
For example, consider a date picker. Quite often, whether trying to
make dates or selling flights, there is a known set of
(non-consecutive) days that are possible, so
Reading 4.10.7.1.15 on the Color state of the input element, I miss a
possibility how to define a set of allowed colors. For other states of
the input element there are such possibilities, such as setting min, max
and step attributes for input type=date.
As UAs are encouraged to provide a
Am 01.03.2011 19:36 schrieb Aryeh Gregor:
Two or three weeks ago I began writing a specification for
execCommand() and related functions. I don't have anything
implementable yet -- it's very incomplete and there are known issues
with the existing stuff. But I thought I'd post it for any early
Am 03.03.2011 20:53 schrieb Aryeh Gregor:
I get the hand-editing argument.b is much nicer to hand-edit than
span style=font-weight: bold, and also fewer bytes. But why would
anyone wantspan style=font-weight: bold?
pbText/b/p is even fewer bytes and more readable than p
Am 04.03.2011 19:58 schrieb Aryeh Gregor:
2) In CSS mode, use CSS where the tag isn't conforming (font, etc.)
or there is no tag (like hiliteColor).
3) In non-CSS mode, use tags where available even if not conforming
(font, etc.), and only use CSS if there's no tag for the feature
(like
Am 28.02.2011 19:56 schrieb Tab Atkins Jr.:
I believe you're arguing that the wrapper semantic, being similarly
ubiquitous, thus needs its own new element as well. What you're
missing is that the wrapper semantic is precisely whatdiv already
expresses.
I do understand usuario's wrapper
Am 01.03.2011 23:50 schrieb Jordan Dobson:
On Tue, Mar 1, 2011 at 2:03 PM, Markus Ernstderer...@gmx.ch wrote:
Am 28.02.2011 19:56 schrieb Tab Atkins Jr.:
I believe you're arguing that the wrapper semantic, being similarly
ubiquitous, thus needs its own new element as well. What you're
Am 18.01.2011 18:11 schrieb Zachary Ozer:
Currently, there's no way to stop / limit the browser from buffering -
once you hit play, you start downloading and don't stop until the
resource is completely loaded. This is largely the same as Flash, save
the fact that some browsers don't respect the
Am 17.01.2011 17:41 schrieb Jeroen Wijering:
Hello all,
We are getting some questions from JW Player users that HTML5 video is quite
wasteful on bandwidth for longer videos (think 10min+). This because browsers
download the entire movie once playback starts, regardless of whether a user
Am 31.12.2010 17:30 schrieb Benjamin Hawkes-Lewis:
On Fri, Dec 31, 2010 at 3:17 PM, Martin Janeckewhatwg@kaor.in wrote:
[snip]
Apart from informing human readers about the correct reproduction of a
misspelled word, a HTMLsic would indicate the same to web applications.
Think of a search
Am 09.12.2010 00:12 schrieb Boris Zbarsky:
On 12/8/10 5:29 PM, Markus Ernst wrote:
Thus, I'd consider an api for detecting the visibility state of every
HTML element useful (totally visible, partially visible, hidden - or a
percentage value).
This is pretty hard to implement, in general
Am 09.12.2010 07:12 schrieb Boris Zbarsky:
2) There is some potential for abuse (e.g. putting up dialogs to make
yourself the active tab if you determine that you aren't, though
perhaps this is a quality of implementation issue). I can
particularly see things like ads doing this so you don't
Am 08.12.2010 21:40 schrieb Bjartur Thorlacius:
On Wed, 08 Dec 2010 19:47:34 -, Alex Komoroske
In particular, there is currently no good way for a web page to detect
that
it is a background tab and is thus completely invisible to the user,
Minor semantic nitpick: please use the term /does
Am 28.11.2010 17:27 schrieb Adrian Sutton:
On 28 Nov 2010, at 15:52, Benjamin Hawkes-Lewis wrote:
On Sun, Nov 28, 2010 at 3:41 PM, Adrian Sutton
adrian.sut...@ephox.com mailto:adrian.sut...@ephox.com wrote:
User's expect a rich text editor
to override the browser default context menu to
Am 25.11.2010 13:21 schrieb Biju:
On Thu, Nov 25, 2010 at 3:41 AM, a...@ashleysheridan.co.uk
a...@ashleysheridan.co.uk wrote:
Modal dialogues have a very special purpose, which works consistently across
various browsers in that we can program in with javascript some very
specific responses.
Am 25.11.2010 17:12 schrieb Nikita Popov:
On 25.11.2010 15:55, Biju wrote:
The request I put is NOT about whether you can make it PRETTY looking
or not.
Sorry, that was how I understood point 1 your initial message.
The question is about why we are allowing website have something which
is
Am 16.11.2010 00:32 schrieb Ian Hickson:
On Wed, 11 Aug 2010, Markus Ernst wrote:
Am 11.08.2010 00:24 schrieb Ian Hickson:
On Mon, 5 Jul 2010, Markus Ernst wrote:
[...]
Example: http://test.rapid.ch/de/haendler-schweiz/iseki.html (This is
under construction.) As a workaround to the height
Am 16.11.2010 19:12 schrieb Tab Atkins Jr.:
On Tue, Nov 16, 2010 at 10:06 AM, Boris Zbarskybzbar...@mit.edu wrote:
On 11/16/10 12:56 PM, Tab Atkins Jr. wrote:
- it is applicable at the client side without scripting
This is not possible, for the simple reason that the whole point of
CORS is
Am 31.08.2010 22:21 schrieb Martin Janecke:
Am 31.08.10 21:40, schrieb Aryeh Gregor:
On Tue, Aug 31, 2010 at 5:25 AM, Martin Janeckewhatwg@kaor.in
wrote:
Besides,time2010/time in a British news article would allow
users e.g.
in Japan to have these dates displayed as 平22年. That's clearly
Am 16.08.2010 11:23 schrieb Maciej Stachowiak:
- Is it a genuinely useful feature?
Yes, the ability to get plaintext content as rendered is a useful
feature and annoying to implement from scratch. To give one very
marginal data point, it's used by our regression text framework to
output
Am 11.08.2010 00:24 schrieb Ian Hickson:
On Mon, 5 Jul 2010, Markus Ernst wrote:
[...]
Example: http://test.rapid.ch/de/haendler-schweiz/iseki.html (This is
under construction.) As a workaround to the height problem, I applied a
script that adjusts the iframe height to the available height
Section 4.8.1.1.9 describes how alternative text for content images
should be written:
http://www.w3.org/TR/html5/embedded-content-1.html#a-key-part-of-the-content
Then, there is a general guideline about writing alternative texts in
section 4.8.1.1.12: A corollary to this is that the alt
Am 02.08.2010 18:21 schrieb Michael Kozakewich:
Dennis wrote:
Yes, but that wouldn't help since I want to force downloads regardless
of the browser settings. Maybe it would do if the type was set to
application/octet-stream, since those, by default, always get downloaded.
People don't often
Am 01.08.2010 11:43 schrieb Tantek Çelik:
http://wiki.whatwg.org/wiki/Img_Alt
I encourage fellow web authors to add opinions/comments.
My personal opinion on the alt attribute is that:
- it should only be used if the image is crucial for understanding the
content, or for navigation (such as
Am 06.07.2010 22:41 schrieb Ashley Sheridan:
On Tue, 2010-07-06 at 16:17 -0400, Aryeh Gregor wrote:
On Tue, Jul 6, 2010 at 6:49 AM, Markus Ernst derer...@gmx.ch
mailto:derer...@gmx.ch wrote:
My problem is this sentence in the spec for seamless: This will cause links
to open in the parent
1 - 100 of 164 matches
Mail list logo
