[webkit-dev] Touch operation corrupts screen when specifying other than overflow:visible in css
Hi, On a windows 7 tablet, PAN operation(=scroll) causes corruption of screen. Does anybody know how to resolve this or have the fix? How to reproduce. 1. Prepare a HTML contents which have an element specifying other than visible to the property overflow in css. 2. Load the contents with webkit 3. Operate the touch operaion, PAN on the element. Problem The content in the element protrudes outside the placeholder for it and can disappear. The build version Webkit.exe on r131112 for Nightly builds We guess Source\WebKit\win\WebView.cpp has some bugs on this issue. Here is the sample contents to reproduce problem. You will see the problem if you PAN on the field for overflow:auto. -- HTML HEADTITLEpan with css:overflow/TITLE/HEAD BODY font size=+2 div style=border: 2px solid blue; padding: 5px 5px 5px 5px; overflow:visible; overflow:visible /div br div style=border: 2px solid red; padding: 5px 5px 5px 5px; overflow:auto; overflow:auto /div /font /BODY /HTML -- Hideki *** Hideki Yoshida Embedded Software Division NEC System Technologies, Ltd. E-MAIL:yoshida-...@necst.nec.co.jp *** ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] [chromium] as of r131699, the chromium port no longer uses any baselines from LayoutTests/platform/mac
All of the Chromium ports will use baselines in their port-specific directories, then fall back through various paths to platform/chromium and then to next to the test. Which means you Apple folks can feel free to break things in platform/mac to your hearts' content :). Let me know if you see any weirdness or problems. Thanks! -- Dirk ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] [chromium] as of r131699, the chromium port no longer uses any baselines from LayoutTests/platform/mac
Does that mean our fallback graph is now finally a tree?? :) https://docs.google.com/drawings/d/1z65SKkWrD4Slm6jobIphHwwRADyUtjOAxwGBVKBY8Kc/edit On Wed, Oct 17, 2012 at 8:15 PM, Dirk Pranke dpra...@chromium.org wrote: All of the Chromium ports will use baselines in their port-specific directories, then fall back through various paths to platform/chromium and then to next to the test. Which means you Apple folks can feel free to break things in platform/mac to your hearts' content :). Let me know if you see any weirdness or problems. Thanks! -- Dirk ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] [chromium] as of r131699, the chromium port no longer uses any baselines from LayoutTests/platform/mac
We should update the graph. It might be a tree now. The only complication might be the wk2 baselines. Adam On Wed, Oct 17, 2012 at 9:53 PM, Eric Seidel e...@webkit.org wrote: Does that mean our fallback graph is now finally a tree?? :) https://docs.google.com/drawings/d/1z65SKkWrD4Slm6jobIphHwwRADyUtjOAxwGBVKBY8Kc/edit On Wed, Oct 17, 2012 at 8:15 PM, Dirk Pranke dpra...@chromium.org wrote: All of the Chromium ports will use baselines in their port-specific directories, then fall back through various paths to platform/chromium and then to next to the test. Which means you Apple folks can feel free to break things in platform/mac to your hearts' content :). Let me know if you see any weirdness or problems. Thanks! -- Dirk ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
