On Mon, 04 Nov 2013 09:52:20 +0100, Domenic Denicola
wrote:
As for *where* the work is done, I will be working within the context of
the WHATWG to produce this specification. My understanding is that
usually the W3C picks some point in time to fork WHATWG specifications
into W3C ones, ch
It seems either http://dev.w3.org/geo/api/spec-source-orientation.html
or https://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html
needs to define and standardize the proprietary window.orientation
feature because not having it defined is a problem:
https://bugzilla.mozilla.org/show_bug
They are somewheat different things. The former is basically a way to get
accelerometer info (useful for games etc) and the latter is about actual
OS(/Screen) orientation, in which the window.orientation (Browser
orientation) falls.
Kenneth
On Tue, Nov 5, 2013 at 12:03 PM, Anne van Kesteren wro
On Tue, Nov 5, 2013 at 11:23 AM, Kenneth Rohde Christiansen
wrote:
> They are somewheat different things. The former is basically a way to get
> accelerometer info (useful for games etc) and the latter is about actual
> OS(/Screen) orientation, in which the window.orientation (Browser
> orientatio
FYI, I added a branch named "Preview version" into which suggestions are
incorporated aggressively to see how the API surface would be change.
https://dvcs.w3.org/hg/streams-api/raw-file/tip/preview.html
Please take a look if you're interested in.
For stabler version edited after having discussion
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23234
Anne changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23724
Bug ID: 23724
Summary: Merge skip() method into read() by adding "none" type
to StreamReadType
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: A
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23725
Bug ID: 23725
Summary: Consider strongly-defined createStream to add generic
stream support for APIs
Product: WebAppsWG
Version: unspecified
Hardware: PC
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23726
Bug ID: 23726
Summary: Integration between XMLHttpRequest and Streams API
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Seve
On Wed, Oct 30, 2013 at 7:19 PM, pira...@gmail.com wrote:
> What you are asking for could be fixed with redirects, that it's the
> HTTP equivalent of filesystems symbolic links :-)
>
Is your suggestion that Google consolidate all its domains into one?
These are widely separated servers (internet
On Thu, Oct 31, 2013 at 2:12 AM, Brian Stell wrote:
> There could be *dozens* of copies of exactly the same a Javascript library,
> shared CSS, or web font in the FileSystem.
Check out the cache part of
https://github.com/slightlyoff/ServiceWorker/ Combined with a smart
implementation that will d
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23731
Bug ID: 23731
Summary: [Streams API] Should readEncoding be merged into
readType?
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23732
Bug ID: 23732
Summary: [Streams API] Consider adding best-effort
scatter/gather mode
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
I like Git's model :-)
This would de-dup the file storage but won't it require downloading it for
every domain (when the data is not lingering in HTTP cache)?
On Tue, Nov 5, 2013 at 11:45 AM, Tim Caswell wrote:
> If the backend implementation used something like git's data store then
> dupli
On Tue, Nov 5, 2013, at 22:35, Anne van Kesteren wrote:
> On Tue, Nov 5, 2013 at 11:23 AM, Kenneth Rohde Christiansen
> wrote:
> > They are somewheat different things. The former is basically a way to get
> > accelerometer info (useful for games etc) and the latter is about actual
> > OS(/Screen)
On Tue, Nov 5, 2013 at 11:06 PM, Mounir Lamouri wrote:
> I remember that Mozilla was not interested in implementing
> window.orientation for various reasons. Has that position changed? I
> would understand that Mozilla wants to implement that for compat reasons
> and if that the case, I would glad
True Kenneth,
- but in all cases, it would be good if anything related to orientation
(Media Query, accelerometer, etc.) at least had a common holistic way of
defining "what is up" ~ (x,y,z) = (0,1,0) or so . and if that *changes* if
the different levels of orientation (device lock, window, etc.)
On Tue, Nov 5, 2013 at 3:27 PM, Anne van Kesteren wrote:
> On Tue, Nov 5, 2013 at 11:06 PM, Mounir Lamouri wrote:
>> I remember that Mozilla was not interested in implementing
>> window.orientation for various reasons. Has that position changed? I
>> would understand that Mozilla wants to impleme
On Wed, Nov 6, 2013, at 11:17, Jonas Sicking wrote:
> Last I looked the property was useless because window.orientation=0
> meant different things on different devices. I.e. on some devices it
> meant "landscape mode" and others it meant "portrait mode".
Indeed, if I remember correctly, window.ori
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22093
Takayoshi Kochi changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22059
Takayoshi Kochi changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23735
Bug ID: 23735
Summary: [Streams API] Failure signaling to object URL created
from Stream
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23736
Bug ID: 23736
Summary: [Streams API] Add fork() method instead of having
pipe(Stream[]) overload
Product: WebAppsWG
Version: unspecified
Hardware: All
OS:
23 matches
Mail list logo