step (in GPU/by the OS)? It would make all current web
content render consistently as expected. Support for the niche use case of true
display of full gamut of wider-than-sRGB profiles can be added less urgently.
--
Kind regards, Kornel
ile seems OK to me. It'd mean the
website already knows how to convert colors to the given colorspace, and the
same profile could be passed back by toDataURL().
--
Kind regards, Kornel
?format=svgtint=fff1e0,fff1e0source=example
For this case Safari requires theme-color to be changed to black, but that
would make the entire UI of Chrome for Android black, which is also
unacceptable.
--
Kind regards, Kornel Lesiński
(authors that mixed colors against the advice would get one color that is a
blend).
And all this would be achieved without the need for another metatag, and the
mask icon would the same in other browsers.
--
Kind regards, Kornel Lesiński
`icon-mask` link relationship for an icon that
user agent can colorize:
link rel=icon-mask href=silhouette.svg
This way authors can control whether they want the icon to be reused as a
regular icon, with link rel=icon icon-mask, or not, by using this
relationship alone.
--
Kind regards, Kornel
).
For server push we already have Server-Sent Events:
https://html.spec.whatwg.org/multipage/comms.html#server-sent-events
I’m not really concerned with how this is solved, but an example would be to
add to XMLHTTPRequest:
XHR is dead.
https://fetch.spec.whatwg.org/
--
regards, Kornel
independently (without needing to create an iframe to get their own lock),
and can't release any other component's lock.
--
regards, Kornel
cpuLock = new navigator.CpuLock();
cpuLock.setThreadPriority(low); // completely made-up API
--
regards, Kornel
it's less clear cut. I think tying it to a notification may be a
good idea. Alternatively, perhaps the lock itself could be an instance of the
progress element that author is supposed to insert to the document? ;)
--
regards, Kornel
On Monday, August 18, 2014 at 6:24 PM, Kornel Lesiński wrote:
I think it'd be unfortunate if this API had just one shared lock per
browsing context and required components on the page to coordinate locking,
but provided no means to do so.
The API allows scripts to check which locks
that conflates all lock types makes extensibility uglier. You won't be able to
elegantly add methods that are valid only for some types of locks, e.g. `new
WakeLock(cpu).dimScreen()` is nonsense, but would valid from perspective of
WebIDL and JS prototypes.
--
regards, Kornel
, and it can result
in wildly different visual quality, file size and time taken to compress the
image.
--
regards, Kornel
[1] https://github.com/pornel/zopfli
properly on the main thread/when layout is
calculated, etc.
exit this sub-algorithm will either cause an earlier source that has
unambiguously matched to be loaded or empty source set will cause
selection algorithm to do nothing.
--
regards, Kornel
(...whatever) {
return Array.from(this).forEach(...whatever);
}
etc.
--
regards, Kornel Lesiński
date pickers are grids with a month view
could style specific pseudo-elements for this layout and mobile browsers
could ignore these styles completely.
--
regards, Kornel
that easy enough).
--
regards, Kornel
).
--
regards, Kornel
On 25 November 2013 10:59:15 Yoav Weiss y...@yoav.ws wrote:
On Mon, Nov 25, 2013 at 11:32 AM, Kornel Lesiński kor...@geekhood.netwrote:
If picture was explicitly controlled by img then websites could start
depending on that behavior, and we'd be stuck with it. OTOH picture can
have native
on img that
conflict with picture's definitions.
--
regards, Kornel
they need to emulate img alt
for existing screen readers or accessibility APIs).
I've dropped usemap. It could be added, but I'm not sure if there is need
for it.
I've specified very few IDL attributes. This area may need to be extended.
--
regards, Kornel
to
convince them otherwise, but until then your best bet is to use
server-side templating language (or project-wide find and replace) to
define your breakpoints once.
--
regards, Kornel
the effort.
--
regards, Kornel
for an attribute, but
instead of using custom attribute parser you read attributes from child
nodes.
--
regards, Kornel
even need to expose that fact to the authors.
--
regards, Kornel
.html
--
regards, Kornel
into multiple
attributes on source to be introduced gradually later/as needed (e.g.
source media, source sizes, source 3d-google-glass-hologram-set,
etc.) without risking explosive complexity of combined microsyntaxes.
--
regards, Kornel
in RICG
years ago, so hopefully we'll eventually come to the same conclusions as
RICG did ;)
--
regards, Kornel
is
it going to be :(
--
regards, Kornel
expressed that they prefer picture syntax over
src-N.
--
regards, Kornel
that sites which don't like being zoomed in would just block it
via meta viewport.
--
regards, Kornel
.
For 1-pixel lines it could be fixed by allowing authors to specify that
path should be stroked with lines aligned to inside/outside of the path
(which is a useful feature on its own).
--
regards, Kornel
as the height of the dependency tree).
So I think that eventually ES6 modules + link[rel=subresource] could be
the answer. The link would expose URLs to (pre)load for performance, but
modules would handle actual loading/execution for flexibility and
reliability.
--
regards, Kornel
[1
-stuff /
--
regards, Kornel
at this point --
It would be nice if the browser also deferred rendering of the element
until scripts that depend on it are run to avoid Flash of Unbehaviored
Content (e.g. elements listed in dependencies have display:none until
scripts are run).
--
regards, Kornel
',
autorotation:false})
--
regards, Kornel
of having rel=subresource for
all script elements.
--
regards, Kornel
alt=
(presentational image).
picture --role=img--/picture would be equivalent to img (missing
alt).
picture --role=img--alternative/picture would be equivalent to img
alt=alternative (alternative present).
--
regards, Kornel
screen, not even 2x
yet.
--
regards, Kornel
heuristics
and accepted risk of loss, e.g. don't snapshot for 1/10th of a second
after canvas has been cleared, don't log commands from
requestAnimationFrame() etc.
--
regards, Kornel
. draw of video) is executed,
3. snapshot,
4. empty the buffer
5. goto 2
That could make readbacks much less frequent. Would this still be a
prohibitively expensive solution?
--
regards, Kornel
be accessible.
--
regards, Kornel
content).
The easy workaround for that may be to treat picture fallback/alt
similarly to button content, i.e. just forbid focusable/interactive
elements. Do any UAs allow users to access a in rendered object?
--
regards, Kornel
-perfect designs for 1.25, 1.5, 1.75, 2.25, etc.
--
regards, Kornel
ratios are linear, rounded to nearest integer (i.e. 3x is OK too).
That's quite common in computer science, and not surprising when dealing with
discrete unit like device pixel.
--
regards, Kornel
comma parsed as invalid media query could end up delimiting
sources in some implementations, and then we'll end up with worst of both
worlds (both ambiguous comma and other unintuitive delimiter needed for
web-compat).
--
regards, Kornel Lesiński
think the syntax with separated attributes is less clear
than a microsyntax in a single attribute — list in a single attribute has
obvious ordering and doesn't rely on an ordered set of predefined names.
--
regards, Kornel Lesiński
-in.
I don't know what to do with default-lowres background-image, so maybe
this is an unavoidable problem :(
--
regards, Kornel Lesiński
* ismap
?
Aren't these legacy features?
--
regards, Kornel
of the image.
Same as:
pic src=portraitHD.jpg (orientation:portrait), landscapeHD.jpg,
portrait.jpg 1x (orientation:portrait), landscape.jpg
1xalt text/pic
--
regards, Kornel Lesiński
for size/DPI of iPhone and
iPad and never supply images for 3000 other resolutions of various Android
devices.
--
regards, Kornel
Sorry, I forgot to clarify this ― I had in mind adding width/height on each
source element, not on picture.
--
regards, Kornel
On 22 maj 2012, at 16:01, Maciej Stachowiak m...@apple.com wrote:
On May 21, 2012, at 9:37 PM, Kornel Lesi��ski kor...@geekhood.net wrote:
There’s no prior
On 22 maj 2012, at 15:57, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Tue, May 22, 2012 at 7:26 AM, Kornel Lesi��ski kor...@geekhood.net wrote:
I think that 3x device is very very unlikely to ever happen, since 2x
screens are may be dense enough to have pixels smaller than human eye can
adding `width` and `height` attributes on the element
(similar to `img`) might solve this, in the event that the author wants
to rely on an intrinsic size instead of CSS?
I think that is a very good idea. Having option to do so is good for
performance, as it avoids reflows.
--
regards, Kornel
On 19 maj 2012, at 10:46, Matthew Wilcox m...@matthewwilcox.com wrote:
On 19 May 2012 00:37, Kornel Lesi��ski kor...@geekhood.net wrote:
On Fri, 18 May 2012 23:11:45 +0100, Matthew Wilcox m...@matthewwilcox.com
wrote:
picture in its current form is unable to support bandwidth-based
of caches that should be taken into
account.
So please specifically address cases I've listed in my previous email.
--
regards, Kornel
On 18 maj 2012, at 10:52, Matthew Wilcox m...@matthewwilcox.com wrote:
Thanks for all the feedback everyone.
I don't think it's going to stop people trying
issues on the Responsive Images group's
mailinglist, but got no constructive feedback.
--
regards, Kornel Lesiński
explained it in more detail previously (using srcset as an example,
but it all applies to min-device-pixel-ratio: MQ as well)
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-May/036051.html
--
regards, Kornel Lesiński
-bandwidth connections (satellite, 3G/4G) it may
already be cheaper to download all versions of all images than to wait for
CSS to be able to select the right ones to load. Solution that requires
page layout for image loading is a step backwards for performance.
--
regards, Kornel Lesiński
it was for
media=(case: breakpoint1) in source.
--
regards, Kornel Lesiński
low-end design and
re-download all images in poor quality?
--
regards, Kornel
scale to be specified, so this change doesn't
take any functionality away.
--
regards, Kornel Lesiński
with fluid main column)
or if your page header adapts to portrait orientation, but images in main
content only adapt to width?
--
regards, Kornel Lesiński
is already claimed to be perfect (Retina
display).
--
regards, Kornel Lesiński
(orientation:landscape)
/header
acticle
img src=illustration-big srcset=illustration-small
(max-width:1000px)
/article
How would you do that with breakpoints?
--
regards, Kornel Lesiński
we will avoid
the problem entirely. But as I've explained above, it's an inconvenient
scaling factor and is likely to overshoot required quality, so 2x is a
safer bet.
But why oh why should we keep 1x as the default if it's going to be the
worst default in any case?
--
regards, Kornel
that the first which
matches at any other density?
--
regards, Kornel Lesiński
to be a
good
default?
Because it's simple (1 image pixel = 1 CSS pixel), and it was the
historical default.
But it's going to become completely useless and nobody is going to use it.
2x default at least has a chance of not being useless.
--
regards, Kornel Lesiński
On Thu, 17 May 2012 19:32:51 +0100, Jeremy Keith jer...@adactio.com
wrote:
Kornel wrote:
Note that the scale multiplier can be omitted already when only the
size is specified
I'm confused by what you mean by scale multiplier. The x value describes
the pixel density of the device/screen
for it, without need to
update code that embeds those images? And is that really saving much
effort? Wouldn't you have to revisit every page anyway to test the new
layout?
[1]http://www.w3.org/community/respimg/2012/05/13/an-alternative-proposition-to-and-srcset-with-wider-scope/
--
regards, Kornel
src=50px-wide-image.png
/picture
/div
--
regards, Kornel Lesiński
be bothered to type extra markup for all vendor's
prefixes in CSS. Nobody bothered with verbose SVG gradient syntax which
was usable before CSS gradients. HTML5 DOCTYPE is loved. Brevity matters.
--
regards, Kornel Lesiński
=(orientation:landscape)
/picture
--
regards, Kornel Lesiński
between author-controlled and
UA-controlled decision.
--
regards, Kornel Lesiński
style=width:100%
--
regards, Kornel Lesiński
information about image. It wouldn't be possible/sensible
to do with a media query.
Even if there was support for something like source
media=user-action:save-as, I can bet that less than 0.5% of pages would
use it and do it correctly.
--
regards, Kornel Lesiński
though both proposals are about selecting right images, their
purposes and requirements are very different.
--
regards, Kornel Lesiński
that specifies
image for higher screen density and/or bandwidth. The point is that
media= would allow author to choose image version adapted to page
layout, and another mechanism connected to source would allow UA to
choose image resolution.
--
regards, Kornel Lesiński
mess with them. Bandwidth/DPI requirements are known to UA
and there can be same set of UA-specific rules that works for all pages.
--
regards, Kornel Lesiński
in alt= wouldn't work well, and
img alt=world map showing most popular browser in each country
doesn't contain the information that the map conveys, so that's at best a
caption, not an alternative.
--
regards, Kornel Lesiński
.
There is no such problem if only same-CSS-pixel-size images are swapped
in-place.
--
regards, Kornel Lesiński
pixels, it could opt to show dog-lo.jpg rather
than dog.jpg.
But still displayed at 960 CSS pixels or course? That'd be fine (and the
UA could even download dog@2x when user zooms in).
--
regards, Kornel Lesiński
information may be the solution:
img srcset=q95percent.jpg size=100KB, q30percent.jpg size=20KB
then UA can easily make decision how much bandwidth it can use (e.g. aim
to download any page in 5 seconds, so try to get image sizes to add up to
less than 5*network B/s).
--
regards, Kornel
=MQ/picture and suffers the same problem of MQ
being inappropriate for bandwidth and relies on authors choosing the right
criteria.
Perhaps there should be an attribute(s) on source that describes
properties of the resource, and could be used for both video and images?
--
regards, Kornel
-and-requirements/
--
regards, Kornel Lesiński
browsers/systems to continue using fake 96dpi/192dpi
snapped to device pixels, and artists to focus only on those ratios. It's
simplest for everybody and gives device-pixel-perfect rendering on varying
screen densities.
--
regards, Kornel Lesiński
and sensible syntax (CSS
@viewport) is not widely supported yet.
However, the design and usability of meta viewport is terrible. You'll
find a lot of pages on the web that get , vs ; wrong in the meta
content.
--
regards, Kornel Lesiński
asynchronously.
--
regards, Kornel Lesiński
and parsing models are
understood.
Dusting off hsub proposal, which doesn't have that problem:
http://www.w3.org/html/wg/wiki/ChangeProposals/hSub
--
regards, Kornel Lesiński
for orientation with simple declaration of adaptive image
resolution (that makes browser automatically take into account screen
size/density and network speed, without needing details spelled out by the
page author).
--
regards, Kornel Lesiński
necessary and only request files that have
changed substantially.
--
regards, Kornel Lesiński
to force it to
switch to a lousy image.
--
regards, Kornel Lesiński
, which makes loading
of JavaScript cleaner than script. Perhaps modules could be loaded
conditionally based on media-query-like declarations?
--
regards, Kornel Lesiński
responsibility with
developers, not browsers).
--
regards, Kornel Lesiński
'autocompletetype' itself gives me an impression of a forced extension,
rather than integral part of the language.
--
regards, Kornel Lesiński
, but uses surname. It would be nice to
rename autocomplete types for consistency with hCard where possible
(unless they're consistent already with something else I don't know :)
--
regards, Kornel Lesiński
. It would be backwards compatible with HTML5 types
and fall back to text for new types or lists.
Having all of type, autocomplete and autocompletetype looks quite messy.
[1]
http://googlewebmastercentral.blogspot.com/2012/01/making-form-filling-faster-easier-and.html
--
regards, Kornel Lesiński
of the encoding compatibility mode by saying meta
charset=utf-8.
Could !DOCTYPE html be an opt-in to default UTF-8 encoding?
It would be nice to minimize number of declarations a page needs to
include.
--
regards, Kornel Lesiński
are comments, or nesting
was done with other purpose in mind).
Therefore I suggest we paint this shed with:
article type=comment
--
regards, Kornel Lesiński
seems relatively useful, given that I use the
barcode/QRCode reader in my phone quite a lot.
Niche needs + inter-app communication sounds like something Web Intents
could do (http://webintents.org).
--
regards, Kornel Lesiński
cases (without breaking links), it needs to be
done at HTTP level, by adding HTTP header (or multipart response? or
attribute to Content-Disposition?) that causes both file download to start
and a page to be displayed at the same time.
--
regards, Kornel Lesiński
1 - 100 of 230 matches
Mail list logo
