Re: [editing] Editing spec is no longer online

It's https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html You're missing the final 'l'. Tim On 6 June 2013 14:08, Johannes Wilm wrote: > This used to work some days ago: > > https://dvcs.w3.org/hg/editing/raw-file/tip/editing.htm > > > Is there a copy anywhere else? > > > -- > Johannes W

Re: [editing] Editing spec is no longer online

ah, thanks. sorry. :) On Thu, Jun 6, 2013 at 9:24 AM, Tim Down wrote: > It's > > https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html > > You're missing the final 'l'. > > Tim > > > On 6 June 2013 14:08, Johannes Wilm wrote: > >> This used to work some days ago: >> >> https://dvcs.w3.org/h

Re: [editing] Editing spec is no longer online

On 6/6/13 9:08 AM, ext Johannes Wilm wrote: This used to work some days ago: https://dvcs.w3.org/hg/editing/raw-file/tip/editing.htm Is there a copy anywhere else? ?

Re: [editing] Editing spec is no longer online

On Thu, Jun 6, 2013 at 2:08 PM, Johannes Wilm wrote: > https://dvcs.w3.org/hg/editing/raw-file/tip/editing.htm You are lacking an l at the end: https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html -- http://annevankesteren.nl/

Re: [editing] Editing spec is no longer online

On 06/06/2013 15:08 , Johannes Wilm wrote: This used to work some days ago: https://dvcs.w3.org/hg/editing/raw-file/tip/editing.htm You're missing an "l" at the end of your link... -- Robin Berjon - http://berjon.com/ - @robinberjon

[editing] Editing spec is no longer online

This used to work some days ago: https://dvcs.w3.org/hg/editing/raw-file/tip/editing.htm Is there a copy anywhere else? -- Johannes Wilm http://www.johanneswilm.org tel US: +1 (520) 399 8880 tel NO: +47 94109013 tel DE: +49 176 370 18082

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

I think what I'm trying to say is that "CSS px units ... independently of the document scale" should be termed "DIPs", and "CSS px units ... given the current document scale" should be termed "CSS pixels", and that it's clearer to think of these as two separate pixel units. And regardless of naming

Re: [css3-mediaqueries][css-device-adapt] Combining @viewport with the Fullscreen API

Yes, for fullscreen you want to be able to control whether it should change orientation or not. Just like a fullscreen HTML5 video playing on the iPhone never changes direction (or at least it didn't use to, don't know about latest version). On my older iPhone, when you click on a HTML5 video eleme

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

You can say that screen.width expresses the screen size in CSS px units and independently of the document scale, unlike window.innerWidth which expresses the amount of CSS px units (horizontally) of the document which you see given the current document scale. Maybe you have suggestions for how to

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

> The innerWidth is showing how many CSS units you are seeing of the contents inside the viewport I agree. My point was that screen.width is measured in DIPs not CSS pixels, and hence screen.width often returns different values from window.innerWidth -- depending on zoom and viewport -- even thoug

Re: [css3-mediaqueries][css-device-adapt] Combining @viewport with the Fullscreen API

On Thu, Jun 6, 2013 at 11:12 AM, Kenneth Rohde Christiansen wrote: > ... Is it accurate to tie this to @viewport? When I rotate my iPhone the chrome also rotates, not just the viewport. -- http://annevankesteren.nl/

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

Hi there On Thu, Jun 6, 2013 at 12:15 PM, John Mellor wrote: > There is a distinction to be made between DIPs and CSS pixels. Take a > portrait iPhone 4 for example: > - screen is 640 device pixels wide > - device pixel ratio is 2 > > CSS pixels are affected by pinch zooming: > > If you use then

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

There is a distinction to be made between DIPs and CSS pixels. Take a portrait iPhone 4 for example: - screen is 640 device pixels wide - device pixel ratio is 2 CSS pixels are affected by pinch zooming: If you use then: - screen.width is fixed at 320 DIPs - document.documentElement.clientWidth

[css3-mediaqueries][css-device-adapt] Combining @viewport with the Fullscreen API

In order for CSS Device Adaptation and Fullscreen to work better together and work with orientation lock in fullscreen mode, I suggest (idea by Rune) we extend the view-mode media feature with the below syntax. I also suggest that we move the view-mode media feature into Media Queries Level 4. @me

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

In order for CSS Device Adaptation and Fullscreen to work better together and work with orientation lock in fullscreen mode, I suggest (idea by Rune) we extend the view-mode media feature with the following syntax @media all and (view-mode: fullscreen(#element1)) { @viewport { orientat

Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

As I understand it, the CSS specs never refer to device pixels, but always to CSS pixels which are basically your DIPs, so the confusion only arises from the fact that browsers did DPI adjustment (upscaled the content to use real CSS values in CSS units - aka DIPs) but forgot to do it for everythin