Hi Xu, Xing, Please find the comments as follows. If you have additional questions, feel free to let me know.
On 07 Aug 2015, 10:37 AM, Xu, Xing <[email protected]> wrote: > Interesting proposal. > I have several questions for this > 1), about "shape-inside" > I think the layout engine and "float" can do this too. If browser knows > that this is a round display, he can promise that everything should be > layout inside the display. There was no way to layout contents inside the display automatically, until now. Instead, authors can use CSS Media Queries that test and query values or features of the user agent or display device, independent of the document being rendered. device-radius can be used to cover this situation, while shape-inside for applying a shape to an element's content area, has another usage. You can check the shape-inside description as follows. https://drafts.csswg.org/css-shapes-2/ Our proposal(css-round-display) is an extension of shape-inside that adds a 'display' value. The original shape-inside could describe shapes like basic-shape(circle(), polygon(), ...) and image(png, gif). If authors specify shape-inside: display, the wrapping contents are easily aligned inside display shape. It could implement by existing method, but it is inconvenient and sometimes almost impossible to define some complicated display shape. In this case, the extension is useful using devices with several display shape, and the devices is becoming more widely available around us. (watches, wearable, appliances, ...) > 2), about "device-radius" > I didn't understand why need this. > Here is my assumption about how to run browser on a round display: > a), Sent a request to server. In the http header part, tell server that I am > a round display. > b), Sever responses with page adapted to round display. > c), browser engine layout/render/paint/composite. > So browser does not need server told him device-radius. Vice versa, server > needs browser inform him about this. The page adapted to round display is made by authors and the authors should use device-radius to distinguish display shapes. All the existing displays have a rectangular shape(TV, monitor, mobile, ...), so it doesn't need to consider the display shape on browsers. As various display shapes have emerged, device-radius property become essential for authors in consideration of the development of adaptive web applications. device-radius is used and processed in browser and is not considered in server side at all. All the CSS core members agreed this fact in regular F2F meeting, and you can see the details as follows. https://drafts.csswg.org/mediaqueries-4/ > 3), layout/composite related code not changed After check your two PR > https://github.com/crosswalk-project/blink-crosswalk/pull/65 > and https://github.com/crosswalk-project/blink-crosswalk/pull/265, I didn't > see any layout/composite related code changed. > So this is still not done? The PR is only related with device-radius, and the others haven't implemented yet. The device-radius' syntax and function is a little simple, so it's good point at base. > -----Original Message----- > From: Crosswalk-dev [mailto:[email protected] > project.org] On Behalf Of Hyojin Song > Sent: Thursday, August 6, 2015 2:51 PM > To: 'Crosswalk-dev' > Subject: [Crosswalk-dev] Intent to Implement: Support the 'device-radius' > media feature in CSS Media Queries > > **Description** > CSS Round Display spec is officially being developed in the W3C CSS > Working Group. > I proposed this spec in CSS working group and became an editor of the > css-round-display spec as follows. > https://drafts.csswg.org/css-round-display/ > > There are several proposed ideas in the specification, and I would like to > contribute the 'device-radius' media feature as one of the CSS Media > Queries' features. This feature has been discussed in the CSS WG mailing > list and F2F meeting so that it has become mature in the process. The > use case of the property is very clear and reasonable as several devices > with round display are recently released. According to the value of > 'device-radius', it could identify the shape of a display such as a rectangle, > a rectangle with rounded corners, a round, and an ellipse. Please find the > details below link. > https://drafts.csswg.org/css-round-display/#device-radius-media-feature > > **Affected component** > chromium-crosswalk, blink-crosswalk > > **Related feature** > XWALK-4734 > https://crosswalk-project.org/jira/browse/XWALK-4734 > > **Target release** > Crosswalk-16 > > **Implementation details** > 1. A new media feature(device-radius) should be supported within CSS > Media Queries syntax. > 2. The algorithm of device-radius is similar to border-radius mechanism > except for a little factors. > - border-radius' specification: > https://drafts.csswg.org/css-backgrounds-3/#the-border-radius > 3. CSS Round Display spec provides more information about principle of > device-radius 4. CSS Round Display: https://drafts.csswg.org/css-round- > display/ > > Thanks, > - hyojin > > _______________________________________________ > Crosswalk-dev mailing list > [email protected] > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
