I make a patch, which adjusts dpi to viewport computation. But, I think this patch needs to be considered further.
I'd like to listen comments.
Created attachment 88790 [details]
Created attachment 88993 [details]
I adjust dpi value of device to viewport computation. And, I modified that EWebLauncher is also changed by the viewport's width / height.
Comment on attachment 88993 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=88993&action=review
> + ecore_evas_resize(app->ee, app->viewport.w + 20, app->viewport.h + 20);
(In reply to comment #3)
> (From update of attachment 88993 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=88993&action=review
> > Tools/EWebLauncher/main.c:275
> > + ecore_evas_resize(app->ee, app->viewport.w + 20, app->viewport.h + 20);
> Seems unrelated
If EWebLauncher size isn't changed, viewport page (e.g, mobile page) is not rendered completely. Because width and height values are changed by dpi value
Created attachment 89118 [details]
Extended Width Page when EWebLauncher is not resized
(In reply to comment #5)
> Created an attachment (id=89118) [details]
> Extended Width Page when EWebLauncher is not resized
If EWebLauncher is not resized, EWebLauncher just shows part of page. Because, width and height is changed by dpi value. As you know, computeViewportAttributes() changes the values. I think it is better to resize EWebLauncher whenever viewport value is changed. How do you think about it ?
Created attachment 89142 [details]
When I resize EWebLauncher's size, page size and device size are changed. Thus, computed viewport width, height values are also more larger because EWebLauncher is more bigger. Eventually, viewport page is not fit to EWebLauncher. Even though there is scroll bar in viewport page, for now, I'd like to add this patch. I'm going to make better solution for this.
Comment on attachment 89142 [details]
Clearing flags on attachment: 89142
Committed r83553: <http://trac.webkit.org/changeset/83553>