Bug 104374
| Summary: | [EFL][WK2] We should consider frame and device scale factors in WebCore instead of scaling our raster graphics engines | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kenneth Rohde Christiansen <kenneth> |
| Component: | WebKit EFL | Assignee: | Mikhail Pozdnyakov <mikhail.pozdnyakov> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | abecsi, cdumez, dongseong.hwang, d-r, joone, jturcotte, kalyan.kondapally, laszlo.gombos, lucas.de.marchi, mikhail.pozdnyakov, noam, ostap73, tmpsantos |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 103105 | ||
Kenneth Rohde Christiansen
Right now we scale externally, by supplying the contents scale (aka frame scale in WebCore terminology) and the device scale directly to our raster engine (cairo_t, QPainter for Qt) instead of letting WebCore handle this like Chrome and Mac ports are doing it.
We should switch so that we align more with other ports, use more common code and gain the advantages of this approach.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Kenneth Rohde Christiansen
cc'ing Mikhail as he is looking into this
Dongseong Hwang
*** This bug has been marked as a duplicate of bug 105978 ***