Re: [webkit-dev] Removal of mediagroup/MediaController from HTML
Hi Anne, You wrote: > Hi, > > The WHATWG is considering removing mediagroup/MediaController from > HTML, since other than WebKit no browser project has expressed > interest in this feature. > > https://github.com/whatwg/html/issues/192 is the corresponding issue. > > I would recommend following up in the issue itself if this is > problematic or if the WHATWG is forgetting something. Thanks for the heads up. Eric & I have followed up there and will continue to monitor the issue. ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] WebCore/platform standalone library
>> >> This almost makes me want to suggest a jokey name for Platform. I can’t >> >> off the top of my head think of a good expansion of OMG, though. Or BBQ. >> > >> > I am not a pro at this, but here are a few tries: Lower-level Object >> > Library. Algorithm Reuse Framework. New Framework for WebCore, New System >> > Framework for WebCore. >> >> Platform Obfuscation Source. > > Platform Interface and Testing Abstraction. General Independent Framework (pronounced "jiff," of course). Low-Level Abstract Platform would also be a logical choice.___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Infinite scrolling feature exploration
Hi, Adam wrote: > Over in Blink-land, we're also quite interested in infinite scrolling. Great! It's an increasingly common pattern that could use some help from the engine. > We've been experimenting with how you might be able to achieve infinite > scrolling using existing web platform API. Cool. I agree with the general principle, but I want to ensure Web authors don't have to roll their own scrolling engine with transforms and rAF just to do interesting things like non-janky infinite scrolling. I think this will require some additions to the platform, but hopefully we can keep the Web-exposed changes minimal. > Do you have a doc that describes the approach you're investigating? I'm in the middle of writing up an email for www-style with our thought process and what we've looked at; stay tuned. Ted ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] New web-facing CSS feature: -webkit-cursor-visibility: auto-hide
Hi Adam, You wrote: > Have you proposed this feature to the relevant standards working > group? Yup! Tantek's gathering proposals for CSS4 UI features on the CSSWG wiki; this proposal is on the list there. Ted ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Removing ENABLE(WEB_INTENTS) code
Hi Nico, You wrote: > I'd like to delete all the ENABLE(WEB_INTENTS) code. As far as I know, > nobody ever shipped this and nobody intents to. Sounds good. Ted ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] new -webkit-user-select value: atomic
Hi, After reviewing the original specification for 'user-select: all' [1], I think the behavior we had in mind for 'user-select: atomic' matches the original intent of 'user-select: all'. It also partially matches the Mozilla behavior, and I believe the differences are likely to be bugs in Mozilla's implementation. I've encouraged Alice to proceed with implementing, using 'all' for the property value, while we continue to work the issue in the CSS WG. Thanks, Ted ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Double-Resolution (Retina) Images - Re: -webkit-image-set
Eric Seidel wrote:
> Assuming I'm understanding Kalle correctly, it seems this could
> already be accomplished with @media resolution?
>
> http://www.w3.org/TR/css3-mediaqueries/#resolution
>
> @media screen and (min-resolution: 264dpi) { … }
>
> Which according to:
> http://en.wikipedia.org/wiki/List_of_displays_by_pixel_density
>
> Would match both the new iPad and the iPhone 4.
As far as the resolution media query is concerned, the resolution of the
new iPad and the iPhone 4 (and anything else with a device-pixel-ratio
of 2) is exactly 192dpi.
This is because the CSS 'dpi' unit is defined to mean dots device pixels
per *CSS inch*, and CSS inches are hardcoded to be 96 CSS pixels.
This means that—without real physical units—the resolution media query
is always redundnant with device-pixel-ratio, which a) we already
implement, and b) is easier to explain to authors than explaining why
both the new iPad and the iPhone 4 are 192 "dpi".
Ted
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Double-Resolution (Retina) Images - Re: -webkit-image-set
Hi Tom, You wrote: > I am seeking feedback for my (hopefully relatively painless in > practice compared to the alternatives - i.e. -webkit-image-set and > html5 ) proposal to solve the problem of 2x-res (double- > resolution) images with our current HTML and CSS standards for devices > with high-resolution displays, such as 3rd Generation iPads and 4th > generation iPhones and newer. webkit-dev probably isn't the best place to design new Web-facing features; in particular, there is ongoing work on this problem space in the CSS WG, the WHATWG, and elsewhere. See for instance the threads starting here http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-February/thread.html#34683 and here http://lists.w3.org/Archives/Public/www-style/2012Feb/thread.html#msg1103 Anybody is welcome to contribute to www-style and the whatwg list. Ted ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] CSS Aspect Ratio Parsing Stage Up For Review
Hi Fady, You wrote: > I've uploaded the parsing stage for the -webkit-aspect-ratio property > that was proposed here: > > http://www.xanthir.com/blog/b4810 […] > I was wondering if anyone would be interested in reviewing this and > getting this incorporated into WebKit? I think we should wait until the aspect-ratio property is incorporated into an Editor's Draft in the CSS WG before exposing an implementation of it to Web content. Also, the CSS Image Values and Replaced Content module already has an object-fit property[1] which WebKit doesn't yet implement. We should probably make a pass at that before having a go at something similar that's not even in an ED. Ted 1. http://dev.w3.org/csswg/css3-images/#object-fit ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Implementing
Ryosuke Niwa wrote: >>> Why do diverge? It seems like we should at least prefix the >>> attribute with webkit in the case spec changes in the future. > >> See above linked discussion for details. In the end we felt limiting >> the selector matching to the scope is more natural, and - with the >> proposed exception providued by :root and :scope - is more flexible. >> >> However, naming the attribute 'webkit-scoped' may certainly be a good >> idea. > > Yes, please use webkitscoped (no - since this is content attribute?). The spec requests that vendor-specific attributes take names of the form "x-vendor-feature": http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#extensibility So x-webkit-scoped would be the way to go. Ted ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
