On Fri, Dec 6, 2013 at 3:24 AM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 12, 2013, at 12:45 AM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 12, 2013, at 8:12 AM, Dimitri Glazkov dglaz...@chromium.org wrote:
1) It is not friendly to ES6 classes. In fact, you can't use class syntax
and this
On Fri, Dec 6, 2013 at 1:37 AM, Ryosuke Niwa rn...@apple.com wrote:
Hi,
Given that many important/natural use cases of custom elements involve
shadow DOM,
can we add a flag to auto-create shadow DOM for custom elements?
In particular, can we add template as the third argument to
If UA controls are not styleable in the manner I wish them to be and I
have access to custom elements + shadow DOM,
I think I would just create my own controls and use them instead of UA ones.
I know it sounds wasteful but I'd imagine that the best ones would end
up being reused much like jQuery
Hi Art, all,
On 11/26/2013 08:43 PM, Arthur Barstow wrote:
Earlier today Travis closed the last open bug for DOM Parsing and
Serialization so this is a Call for Consensus (CfC) to publish a LCWD of
that spec, using the following ED as the basis:
On Fri, Dec 6, 2013 at 5:26 AM, Brian Di Palma off...@gmail.com wrote:
If UA controls are not styleable in the manner I wish them to be and I
have access to custom elements + shadow DOM,
I think I would just create my own controls and use them instead of UA
ones.
And you'll make the
On 12/6/13 7:40 AM, ext Ms2ger wrote:
On 11/26/2013 08:43 PM, Arthur Barstow wrote:
Earlier today Travis closed the last open bug for DOM Parsing and
Serialization so this is a Call for Consensus (CfC) to publish a LCWD of
that spec, using the following ED as the basis:
On Thu, 5 Dec 2013, Jonas Sicking wrote:
I think both are issues. I.e. I think we have two separate use cases:
1. Enable using the built-in rendering of form controls, but style them
using author-supplied CSS.
2. Enable completely replacing the rendering of form controls
I agree and
The custom element draft does add a new synchronization point. After
setting innerHTML (for example), before returning to the script the
callbacks for the custom elements created by innerHTML are called in tree
order.
This does lead to the possibility to observer objects that have not yet had
IndexedDB implementation in Firefox 26 (the current beta) supports a
new storage type called temporary storage.
In short, it's a storage with LRU eviction policy, so the least
recently used data is automatically deleted when
a limit is reached. Chrome supports something similar [1].
Obviously,
On Fri, Dec 6, 2013 at 2:33 AM, Ryosuke Niwa rn...@apple.com wrote:
It appears to me that we should definitely have a good answer for this
question before the specification reaches CR
given that the definition of ES6 classes is pretty stable at this point.
ES6 classes do not introduce any
On Fri, Dec 6, 2013 at 12:59 PM, Scott González
scott.gonza...@gmail.com wrote:
On Fri, Dec 6, 2013 at 5:26 AM, Brian Di Palma off...@gmail.com wrote:
If UA controls are not styleable in the manner I wish them to be and I
have access to custom elements + shadow DOM,
I think I would just
On Fri, Dec 6, 2013 at 10:53 AM, Brian Di Palma off...@gmail.com wrote:
I did mention that these would probably be turned into reusable
components in widget libraries.
If they hope to be used by developers I see no reason why the issues
you raised would not be addressed by those libraries.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24021
Bug ID: 24021
Summary: [Streams API] Fix process pendingWriteQueue alrogithm
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24021
Takeshi Yoshino tyosh...@google.com changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Takayoshi would like to publish a new Working Draft of Input Method
Editor API. This is a Call for Consensus to do so using the following
document as the basis:
https://dvcs.w3.org/hg/ime-api/raw-file/default/TR4.html
Agreement to this proposal: a) indicates support for publishing a new
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24022
Bug ID: 24022
Summary: [Streams API] Lazily encode write()-en DOMString
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24023
Bug ID: 24023
Summary: [Streams API] Returned promise of write() should be
fulfilled with current available space size rather
than how many bytes were written
Product:
On Fri, Dec 6, 2013 at 4:00 PM, Scott González scott.gonza...@gmail.com wrote:
On Fri, Dec 6, 2013 at 10:53 AM, Brian Di Palma off...@gmail.com wrote:
I did mention that these would probably be turned into reusable
components in widget libraries.
If they hope to be used by developers I see no
Thanks for sending this!
On Fri, Dec 6, 2013 at 7:19 AM, Jan Varga jan.va...@gmail.com wrote:
IndexedDB implementation in Firefox 26 (the current beta) supports a new
storage type called temporary storage.
In short, it's a storage with LRU eviction policy, so the least recently used
data
On Fri, Dec 6, 2013 at 5:06 AM, Arthur Barstow art.bars...@nokia.comwrote:
Even worse is the removal of the reference to the source specification,
given that you know that this is a contentious subject in this WG.
Both Travis and I supported keeping that information in the boilerplate.
On Fri, 06 Dec 2013 18:16:06 +0100, Arthur Barstow art.bars...@nokia.com
wrote:
Takayoshi would like to publish a new Working Draft of Input Method
Editor API. This is a Call for Consensus to do so using the following
document as the basis:
On 12/6/13 1:29 PM, Joshua Bell wrote:
// Throws TypeError on older implementations since Dictionary won't
coerce to Number (?)
Sure it will. It'll do ToNumber() and probably end up NaN (which
becomes 0 as an unsigned long long) unless your object has a valueOf
method that returns
On Thu, Dec 5, 2013 at 5:56 PM, Domenic Denicola
dome...@domenicdenicola.com wrote:
From: Jonas Sicking [mailto:jo...@sicking.cc]
The tricky part is finding a set of pseudo elements that work across
different UAs, and that give authors enough control that they can integrate
the control with
On Fri, Dec 6, 2013 at 11:09 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 12/6/13 1:29 PM, Joshua Bell wrote:
// Throws TypeError on older implementations since Dictionary won't
coerce to Number (?)
Sure it will. It'll do ToNumber() and probably end up NaN (which becomes
0 as an
On 12/6/13 2:37 PM, Joshua Bell wrote:
This behavior is specified in prose, not IDL:
https://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html#widl-IDBFactory-open-IDBOpenDBRequest-DOMString-name-unsigned-long-long-version
If the value of version is 0 (zero), the implementation must throw a
On Dec 6, 2013, at 7:37 AM, Erik Arvidsson a...@chromium.org wrote:
On Fri, Dec 6, 2013 at 2:33 AM, Ryosuke Niwa rn...@apple.com wrote:
It appears to me that we should definitely have a good answer for this
question before the specification reaches CR
given that the definition of ES6
fOn Thu, Dec 5, 2013 at 2:14 AM, Ke-Fong Lin ke-fong@4d.com wrote:
1) Sync APIs are inherently easier to use than async ones, and they are
much
less error prone. JS developers are not C++ developers. Whenever
possible, it's
just better to make things more simpler and convenient.
On Wed, Dec 4, 2013 at 4:38 PM, Charles Pritchard ch...@jumis.com wrote:
On 12/4/13, 2:43 AM, Ke-Fong Lin wrote:
IMHO, we should make sync APIs available in both dedicated and shared
workers.
In order of importance:
1) Sync APIs are inherently easier to use than async ones, and they are
On Dec 6, 2013, at 1:20 AM, Brian Di Palma off...@gmail.com wrote:
On Fri, Dec 6, 2013 at 3:24 AM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 12, 2013, at 12:45 AM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 12, 2013, at 8:12 AM, Dimitri Glazkov dglaz...@chromium.org wrote:
1) It is not
On Dec 6, 2013, at 5:01 PM, Ryosuke Niwa rn...@apple.com wrote:
On Dec 6, 2013, at 1:20 AM, Brian Di Palma off...@gmail.com wrote:
On Fri, Dec 6, 2013 at 3:24 AM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 12, 2013, at 12:45 AM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 12, 2013, at 8:12
From: Jonas Sicking [mailto:jo...@sicking.cc]
The control that you see by default can simply be targetted with select, no?
Hmm, I suppose so. Although I have been unable to get rid of the arrow (which I
consider part of that control) with CSS. And, I have found that styles applied
to the
On 12/6/13 10:25 PM, Domenic Denicola wrote:
We can create our own arrows with (multiple) background images, or ::after.
You can, but if it doesn't match the scrollbar width in cases when there
is a scrollbar the result looks pretty terrible when the popup is
opened... And scrollbar widths
On Thu, Dec 5, 2013 at 5:37 PM, Ryosuke Niwa rn...@apple.com wrote:
Hi,
Given that many important/natural use cases of custom elements involve
shadow DOM,
can we add a flag to auto-create shadow DOM for custom elements?
In particular, can we add template as the third argument to
On Dec 6, 2013, at 7:41 PM, Elliott Sprehn espr...@chromium.org wrote:
On Thu, Dec 5, 2013 at 5:37 PM, Ryosuke Niwa rn...@apple.com wrote:
Given that many important/natural use cases of custom elements involve shadow
DOM,
can we add a flag to auto-create shadow DOM for custom elements?
In
On Fri, Dec 6, 2013 at 7:25 PM, Domenic Denicola
dome...@domenicdenicola.com wrote:
From: Jonas Sicking [mailto:jo...@sicking.cc]
The control that you see by default can simply be targetted with select,
no?
Hmm, I suppose so. Although I have been unable to get rid of the arrow (which
I
35 matches
Mail list logo
