On Fri, Jun 24, 2011 at 3:43 PM, Ian Hickson wrote:
> On Fri, 24 Jun 2011, Kenneth Russell wrote:
>>
>> Slightly larger issue. In the typed array spec, views like Float32Array
>> refer to an ArrayBuffer instance. It's desired to be able to transfer
>> multiple views of the same ArrayBuffer in the
On Fri, 24 Jun 2011, Kenneth Russell wrote:
>
> Slightly larger issue. In the typed array spec, views like Float32Array
> refer to an ArrayBuffer instance. It's desired to be able to transfer
> multiple views of the same ArrayBuffer in the same postMessage call.
> Currently, because each Transf
On Thu, Jun 23, 2011 at 4:52 PM, Ian Hickson wrote:
> On Tue, 21 Jun 2011, Ian Hickson wrote:
>>
>> How about we just make postMessage() take the object to clone in the first
>> argument, an array of objects to transfer in the second; on the other
>> side, the author receives the object cloned, wi
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13020
Ms2ger changed:
What|Removed |Added
CC||i...@hixie.ch,
|
On Fri, Jun 24, 2011 at 1:58 PM, Aryeh Gregor wrote:
> But this does highlight the fact that we probably want to support
> mouse-locking that doesn't hide the cursor also, for this kind of
> mouse-based scrolling. In that case, though, the coordinates and
> mouse events should behave just like re
On Wed, Jun 22, 2011 at 5:20 AM, Simon Pieters wrote:
> On Tue, 21 Jun 2011 00:43:52 +0200, Aryeh Gregor
> wrote:
>> There's a middle ground here: you can lock the mouse to the window,
>> but not completely. That is, if the user moves the mouse to the edge,
>> it remains inside, but if they move
On Fri, Jun 24, 2011 at 12:00 PM, Vincent Scheib wrote:
> I've added clarification to the draft spec in the use case section,
> "Touch screen device input
> All the application use cases are relevant on touch screen devices as well.
> A user should be permitted to make large gestures that are int
>
> And what if the device in question is just a touchscreen with no
> keyboard, mouse or hardware buttons?
>From the draft spec: "Touch devices may also choose to reserve a portion of
the touch interface for an unlock gesture."
Mouse lock seems irrelevant on a touchscreen...
I've added clarif
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13042
Anne changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13042
Summary: Define Event.timeStamp
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component:
Hixie, All,
Ian responded [1] to the last set of Server-Sent Events comments I had
noted, and Bugzilla now reports Zarro Boogs [2] for this spec
(11835/Fixed, 11836/WontFix, 12411/Fixed, 12883/WontFix).
As such, this raises the question if the spec is ready for Last Call
Working Draft public
The View Mode Media Feature is commonly used with the device adaption
spec [1]. What would be quite useful would be a way of making respect the widget's width and height (as declared in the
widgets config.xml). My proposal would be to introduce "widget-width"
and "widget-height" to be used as fol
On Fri, Jun 24, 2011 at 12:44 PM, Scott Wilson
wrote:
> On 24 Jun 2011, at 10:41, Marcos Caceres wrote:
>
>> On Fri, Jun 24, 2011 at 11:08 AM, Rich Tibbett wrote:
>>> Marcos Caceres wrote:
On Fri, Jun 24, 2011 at 1:28 AM, Charles Pritchard
wrote:
>
> One issue which comes
On 24 Jun 2011, at 10:41, Marcos Caceres wrote:
> On Fri, Jun 24, 2011 at 11:08 AM, Rich Tibbett wrote:
>> Marcos Caceres wrote:
>>>
>>> On Fri, Jun 24, 2011 at 1:28 AM, Charles Pritchard
>>> wrote:
One issue which comes up is that widget is also used in ARIA to describe
ui elem
On Jun/24/2011 4:50 AM, ext Marcin Hanclik wrote:
Changing it now could confuse the industry even more and will not help, I think.
Agreed, and in the abscence of any new and overwhelmingly compelling new
information, I will object to any name change.
-AB
On Fri, Jun 24, 2011 at 11:08 AM, Rich Tibbett wrote:
> Marcos Caceres wrote:
>>
>> On Fri, Jun 24, 2011 at 1:28 AM, Charles Pritchard
>> wrote:
>>>
>>> One issue which comes up is that widget is also used in ARIA to describe
>>> ui elements.
>>>
>>> I suspect we'll see apps used ubiquitously; wi
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13035
Ms2ger changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
Marcos Caceres wrote:
On Fri, Jun 24, 2011 at 1:28 AM, Charles Pritchard wrote:
One issue which comes up is that widget is also used in ARIA to describe ui
elements.
I suspect we'll see apps used ubiquitously; widget seems to e reserved to early
experiments in linked apps; apps via iframe.
The problem with widgets is that the name conflicts (or is a bit different
angle) with the UI widgets (or controls) that are also in use (e.g.
wxWidgets, GTK widgets etc.). We could invent some other name (WAF,
WebApplicationPackaging etc. as people quote already), but ...
On the other hand many p
On Fri, Jun 24, 2011 at 1:28 AM, Charles Pritchard wrote:
> One issue which comes up is that widget is also used in ARIA to describe ui
> elements.
>
> I suspect we'll see apps used ubiquitously; widget seems to e reserved to
> early experiments in linked apps; apps via iframe.
>
> Like many on
20 matches
Mail list logo
