Date: Sat, 25 Jan 2014 18:21:59 +0100
From: rasmusf...@gmail.com
...
Device-pixel-ratio can be quite relevant to include in urls; with an 2x
image compression artifacts in lossy formats (jpg, webp) are less visible
which in turn means you can crank up compression without losing visible
There are still some pre-loader issues. Google is promoting that the CDN
dynamically optimize the content, that the user agent share enough info to
allow the CDN to do so - effectively moving a UA function to the cloud and
making a service out of it! From a user privacy perspective this is
Adding 'srcalt' does not seem warranted.
The steps seem too prescriptive for a standard, but might represent one
possible implementation.
I think too much weight is being put on the pre-loader optimization and do not
believe this should block a declarative solution that informs the UA of the
/write? Both humans
and machines.
I won't bother you with all the details here - I've tried to flesh out the
idea in this gist: https://gist.github.com/rasmusfl0e/6727092
On Thu, Dec 12, 2013 at 1:53 AM, Fred Andrews freda...@live.com wrote:
Adding 'srcalt' does not seem warranted
Date: Thu, 17 Jan 2013 20:45:59 +
From: i...@hixie.ch
...
1) This would make it possible to write JavaScript libraries that
seamlessly scan the current page for input type=file and add
integration with Dropbox / Google Drive / Sky Drive etc. I claim that
changing the input
Hi Stan,
From: stas...@orc.ru
...
Subject: Re: [whatwg] API for unique identification of devices
(mobile/tablet/pc)
...
First, I don't think it's convenient for users to register themselves
on many sites, which they visit occasionally. If most of the users do this
right now,
it
Dear Ian,
Thank you opening a discussion about these interactive elements. It would be
disappointing to see these abandoned, for those who would like to see more
interactive non-javascript content.
I would note that CSS alone is able to implement styled menus but only for
'hover to activate'
Date: Thu, 22 Nov 2012 11:23:19 +0100
From: derer...@gmx.ch
...
Maybe, instead of adding that kind of functionalities to form elements,
it might be worth thinking of a different way. E.g., define a set of
scripting actions that are considered as very useful for UIs, and have
no security
.
Fixed.
On Sat, 3 Nov 2012, Fred Andrews wrote:
Feedback and suggestions for appropriate markup to declare web workers
would be appreciated.
Workers are only usable from script, so just start them in script. No need
for anything declarative.
The use case requires a JS context
The canvas that scripts draw into could be over-sized with the UA down sampling
this to
fit the target size and taking into account the sub-pixel screen layout when
doing so.
cheers
Fred
Date: Wed, 14 Nov 2012 11:09:49 -0500
From: ju...@chromium.org
To: rob...@ocallahan.org
CC:
Fred
To: wha...@whatwg.org; freda...@live.com
...
On Sat, 03 Nov 2012 03:29:10 +0200, Fred Andrews freda...@live.com wrote:
...
1. Declarative web worker creation.
Feedback and suggestions for appropriate markup to declare web workers
would be appreciated.
The use case is a document
To: freda...@live.com
CC: wha...@whatwg.org; sim...@opera.com
Subject: Re: [whatwg] Declarative web worker creation and communication?
On Mon, Nov 5, 2012 at 10:24 AM, Fred Andrews freda...@live.com wrote:
Hi Simon,
The use I have in mind is a work-in-progress, see:
http://www.w3.org
1. Declarative web worker creation.
Feedback and suggestions for appropriate markup to declare web workers
would be appreciated.
The use case is a document with JS disabled or restricted so that it can not
create web workers, yet still wants to create web workers to process page
input and to
Hi Ian,
Thank you for taking the time to follow up. Some of my comments do seem a
little immature in hindsight and I tend to agree now that adding a lot of these
suggestions to the HTML spec. would make little difference.
I am exploring options to reduce the potential for UA state leaks
Fred
Date: Thu, 18 Oct 2012 08:31:57 +0200
From: i...@anselm-hannemann.com
To: freda...@live.com
CC: whatwg@lists.whatwg.org; odi...@opera.com
Subject: Re: [whatwg] Features for responsive Web design
Am Donnerstag, 18. Oktober 2012 um 04:05 schrieb Fred Andrews:
This is good point. Could I
This is good point. Could I just clarify my understanding with an example:
Given a thumbnail image with srcset:
srcset=low.jpg 20w, hi.jpg 40w, huge.jpg 80w
The webpage may want to have the browser scale the 20w image to say 50px
without the browser deciding that the 40w image is more
From: m...@apple.com
...
My point is, that any device-specific notation, such as 2x, forces the
author to make decisions that the browser should actually make. The author
does not know if in a few years the image will be viewed with 1.5x or 3x or
7x or whatever devices.
This is
From: m...@apple.com
...
I have always been comfortable with the 'x' part of srcset, but the w
and h part felt somewhat wrong to me. What you'd really want to consider
when deciding which image to pick isn't the size of the viewport itself,
but the size available for the image once the
From: smyl...@stripey.com
...
img style=width: 10em src=image-320x200.jpg
set=image-320x200.jpg 320 200 10k, image-640x400.jpg 640 400 40k,
image-1280x800.jpg 1280 800 150k
The layout size of that img element is not computable until all
external stylesheets have
From: sim...@opera.com
...
On Fri, 07 Sep 2012 06:07:30 +0200, Fred Andrews freda...@live.com wrote:
From: jackalm...@gmail.com
...
I'm not sure how best to solve this, but John Mellor suggested
allowing the specification of the image's native dimensions somehow.
That way
I'm currently building an analysis system like Google Analytics, which
gets embedded into a website via a small JavaScript snippet. When I
analyzed the data, I came across a very interesting trick because I got
a lot of requests (with the data from location.href) where the entire
From: jackalm...@gmail.com
...
I'm not sure how best to solve this, but John Mellor suggested
allowing the specification of the image's native dimensions somehow.
That way, the browser could know that the 1600.jpg image is
appropriate to serve as an 800px wide high-dpi image, or a 1600px
Aug 2012, Fred Andrews wrote:
Agreed. The width and height of the images is what is needed. The
browser needs to fill pixels so needs to know the sizes of the available
images in pixels.
Forget the x scale descriptions and all the other proposed extensions
and just include a set
From: bhawkesle...@googlemail.com
Date: Wed, 29 Aug 2012 08:34:47 +0100
...
Javascript is just too general a programming language for easy management
and is heading in the direction of Java.
I'm not sure how far the problem is Javascript, rather than the
browser and document object
Date: Wed, 29 Aug 2012 10:52:05 -0400
From: bzbar...@mit.edu
...
On 8/29/12 10:15 AM, Fred Andrews wrote:
Yes, but fluid layout could use some calculations and is it likely that
declarative calculations would ever be added to CSS?
You mean other than http://dev.w3.org/csswg/css3
From: bhawkesle...@googlemail.com
Date: Wed, 29 Aug 2012 21:25:07 +0100
...
For example a lot could be done with data-flow computations.
Are you talking about something like the calculate property from XForms?
Something that could handle simple event processing such as drop down
Date: Tue, 28 Aug 2012 21:41:02 +
From: i...@hixie.ch
To: callow_m...@hicorp.co.jp
CC: wha...@whatwg.org
Subject: Re: [whatwg] Why won't you let us make our own HTML5 browsers?
On Fri, 8 Jun 2012, Mark Callow wrote:
On 08/06/2012 06:09, Ian Hickson wrote:
The dire warning
...
But that's exactly my point! The w/h descriptors are sufficient *only* for
art direction, where you want to swap between completely different images
(or at least different crops of the same image), based on viewport size, to
match other changes occurring in your responsive design as the
On Tue, 19 Jun 2012 11:56:04 +0200, Chaals McCathieNevile w...@chaals.com
wrote:
On Fri, 08 Jun 2012 05:05:11 +0200, Mark Callow callow_m...@hicorp.co.jp
wrote:
On 08/06/2012 06:09, Ian Hickson wrote:
The dire warning doesn't work. I'm just saying that's the direction that
operating
29 matches
Mail list logo
