This sounds good to me, but is there any reason why we can't support physical device changes (switching monitors) and support target-densitydpi? This would be highly desirable for us.
Fady == Page::effectiveDeviceScaleFactor == > > Page::effectiveDeviceScaleFactor starts off as matching > Page::deviceScaleFactor but changes to reflect any target-densitydpi > directives. It's unclear to me how Page::effectiveDeviceScaleFactor > should react when the underlying physical device changes its scaling > factor. Currently, that shouldn't occur, so I'm inclined to add an > ASSERT and worry about it later. > > == Settings::defaultDeviceScaleFactor == > > This variable will be deleted. > > Thoughts? > Adam >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
