- 04 Nov, 2014 6 commits
-
-
aelias@chromium.org authored
The pinch viewport visibleRect is snapped to LayoutRect in RenderBox::scrollRectToVisible, but it remained at full precision FloatRect when used in PinchViewport::scrollIntoView. This caused a small scroll in cases that should've been a no-op. This changes PinchViewport::scrollIntoView to cast visibleRect() to a LayoutRect before using it, fixing the issue by making the imprecision cancel out. I also changed the argument rect to a LayoutRect to avoid the reverse problem of too much precision in that one in the future. NOTRY=true BUG=428826 Review URL: https://codereview.chromium.org/678153003 git-svn-id: svn://svn.chromium.org/blink/trunk@184818 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yhirano@chromium.org authored
As the new WebSocket implementation is used as default and the old one was deleted, NewWebSocketChannelImpl is not an appropriate name. BUG=423201 R=ricea@chromium.org Review URL: https://codereview.chromium.org/690883002 git-svn-id: svn://svn.chromium.org/blink/trunk@184817 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
wangxianzhu@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=184812 BUG=386601 TBR=junov@chromium.org Review URL: https://codereview.chromium.org/704473002 git-svn-id: svn://svn.chromium.org/blink/trunk@184816 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
bashi@chromium.org authored
This is a follow-up CL of https://codereview.chromium.org/689013002 v8_union.py and v8_dictionary.py create a same flag from the same condition. This should be a property of IdlType. BUG=240176 Review URL: https://codereview.chromium.org/700603003 git-svn-id: svn://svn.chromium.org/blink/trunk@184814 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
junov@chromium.org authored
BUG=386601 Review URL: https://codereview.chromium.org/687363003 git-svn-id: svn://svn.chromium.org/blink/trunk@184812 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
seanmccullough@chromium.org authored
Adds a link in the toolbar to http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium BUG=420469 Review URL: https://codereview.chromium.org/696813002 git-svn-id: svn://svn.chromium.org/blink/trunk@184811 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 03 Nov, 2014 25 commits
-
-
skobes@chromium.org authored
BUG=417782 Review URL: https://codereview.chromium.org/691863003 git-svn-id: svn://svn.chromium.org/blink/trunk@184810 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jrummell@chromium.org authored
EME tests were changed to avoid the problem where a message event occurs before the second needkey event. Removing the tests that had this issue from the list of flaky tests. BUG=407993 TEST=flakiness dashboard all green for these tests Review URL: https://codereview.chromium.org/700663003 git-svn-id: svn://svn.chromium.org/blink/trunk@184809 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
timloh@chromium.org authored
getPropertyCSSValue, CSSValue, etc. are no longer exposed to the web. This patch removes the tests which exist only to test this functionality. BUG=428595 Review URL: https://codereview.chromium.org/689323002 git-svn-id: svn://svn.chromium.org/blink/trunk@184808 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
morrita@chromium.org authored
TBR=horo@chromium.org BUG=429874 NOTRY=true Review URL: https://codereview.chromium.org/686343003 git-svn-id: svn://svn.chromium.org/blink/trunk@184807 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
avayvod@chromium.org authored
BUG=412331 Review URL: https://codereview.chromium.org/685263003 git-svn-id: svn://svn.chromium.org/blink/trunk@184806 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
morrita@chromium.org authored
NOTRY=true TBR=aberent@chromium.org BUG=429843 Review URL: https://codereview.chromium.org/697253002 git-svn-id: svn://svn.chromium.org/blink/trunk@184805 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rob.buis@samsung.com authored
This early return was protecting against SVG Font usage, however SVG Fonts were removed in https://codereview.chromium.org/656913006, so convert into an ASSERT instead and remove the outdated comment. Review URL: https://codereview.chromium.org/684463004 git-svn-id: svn://svn.chromium.org/blink/trunk@184804 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
watk@chromium.org authored
Previously when an HTMLMediaElement received focus, the media controls would be shown regardless of whether 'controls' was set. It's possible for an HTMLMediaElement to receive focus despite not having 'controls' set, if it has a 'tabindex'. BUG=424625 Review URL: https://codereview.chromium.org/692643002 git-svn-id: svn://svn.chromium.org/blink/trunk@184803 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
morrita@chromium.org authored
Revert of The name attribute can be from contents for listitem role (patchset #1 id:1 of https://codereview.chromium.org/696953002/) Reason for revert: This seems breaking AccessibilityAriaList in content_browsertests on Mac. http://build.chromium.org/p/chromium.webkit/builders/Mac10.6%20Tests/builds/27219 http://test-results.appspot.com/dashboards/flakiness_dashboard.html#master=chromium.webkit&testType=content_browsertests&tests=DumpAccessibilityTreeTest.AccessibilityAriaList Original issue's description: > The name attribute can be from contents for listitem role > according to http://www.w3.org/WAI/PF/aria/roles#listitem. > > BUG=347865 > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=184795 TBR=dmazzoni@chromium.org,je_julie.kim@samsung.com NOTREECHECKS=true NOTRY=true BUG=347865 Review URL: https://codereview.chromium.org/703473002 git-svn-id: svn://svn.chromium.org/blink/trunk@184802 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
wangxianzhu@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=184794 BUG=407416 TBR=jchaffraix@chromium.org Review URL: https://codereview.chromium.org/697433004 git-svn-id: svn://svn.chromium.org/blink/trunk@184799 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
robhogan@gmail.com authored
When we start the selection range in an element the selection is taken to include its :before or :after pseudoelement. So likewise when we modify the selection to an element on a line boundary that selection should include its :before/:after pseduoelements. BUG=342574 Review URL: https://codereview.chromium.org/693283002 git-svn-id: svn://svn.chromium.org/blink/trunk@184798 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rtoy@chromium.org authored
The new error message makes it clear why createMediaElementSource is throwing an error instead of the previous generic "invalid". Also simplify the layout test implementation to also show the errors thrown. No functional changes. BUG=429204 Review URL: https://codereview.chromium.org/692213004 git-svn-id: svn://svn.chromium.org/blink/trunk@184797 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jvanverth@google.com authored
Preliminary work before we turn on distance field rendering for small paths (e.g. icons). Any paths marked volatile will not be cached in the distance field path system. Canvas paths are temporary, so they should be marked as such. BUG=417817 Review URL: https://codereview.chromium.org/696443002 git-svn-id: svn://svn.chromium.org/blink/trunk@184796 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
je_julie.kim@samsung.com authored
according to http://www.w3.org/WAI/PF/aria/roles#listitem. BUG=347865 Review URL: https://codereview.chromium.org/696953002 git-svn-id: svn://svn.chromium.org/blink/trunk@184795 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jchaffraix@chromium.org authored
https://codereview.chromium.org/620553009 moved some of the selection-related invalidations to the invalidation phase. This change fixes the original logic that wasn't totally right. The core issue is that we have to store the old selection rectangle as we can't compute it as part of the next frame (all the selection information have been updated by then). This change also includes some simplification of the selection code now that we don't need much of the logic. BUG=407416 Review URL: https://codereview.chromium.org/665673004 git-svn-id: svn://svn.chromium.org/blink/trunk@184794 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
hans@chromium.org authored
It was failing to link due to multiple definitions of memory allocation functions (in both 32- and 64-bit builds). It seems we don't have any buildbots exercising this configuration. BUG=429498 Review URL: https://codereview.chromium.org/696233002 git-svn-id: svn://svn.chromium.org/blink/trunk@184793 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pfeldman@chromium.org authored
BUG=424191 Review URL: https://codereview.chromium.org/697563003 git-svn-id: svn://svn.chromium.org/blink/trunk@184792 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
wangxianzhu@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=184788 BUG=392311 TBR=mayurk.vk@samsung.com Review URL: https://codereview.chromium.org/701483003 git-svn-id: svn://svn.chromium.org/blink/trunk@184791 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rob@robwu.nl authored
BUG=423270 NOTRY=true TBR=abarth@chromium.org Review URL: https://codereview.chromium.org/699583002 git-svn-id: svn://svn.chromium.org/blink/trunk@184789 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mayurk.vk@samsung.com authored
This CL shows a message in developer tools console, warning that the sync xhr may hamper responsiveness. This was shown as per the spec suggestion: https://xhr.spec.whatwg.org/#sync-warning BUG=392311 Review URL: https://codereview.chromium.org/585873002 git-svn-id: svn://svn.chromium.org/blink/trunk@184788 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
r.nagaraj@samsung.com authored
Move the v8::Isolate* parameter to the first parameter of various binding methods in third_party/WebKit/Source/bindings This step is to move the v8::Isolate* parameter to the first parameter of various binding methods in third_party/WebKit/Source/bindings (Ref: binding-methods changed: static void installV8TestInterfaceTemplate(v8::Handle<v8::FunctionTemplate>, v8::Isolate*) inline void setObjectGroup(ScriptWrappableBase* scriptWrappableBase, const v8::Persistent<v8::Object>& wrapper, v8::Isolate* isolate) static void visitDOMWrapper(ScriptWrappableBase*, const v8::Persistent<v8::Object>&, v8::Isolate*) typedef void (*ResolveWrapperReachabilityFunction)(ScriptWrappableBase* internalPointer, const v8::Persistent<v8::Object>&, v8::Isolate*)) BUG=424446 Review URL: https://codereview.chromium.org/696203002 git-svn-id: svn://svn.chromium.org/blink/trunk@184787 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rosca@adobe.com authored
Due to the specification, filters and masking should be applied before blending. I added hasBlendMode as a conjunction for RenderLayer::isTransparent(). An element with mix-blend-mode will let the colors behind it to be visible in some way, so I think it the element with blend modes can be seen as transparent. BUG=425580 Review URL: https://codereview.chromium.org/670753002 git-svn-id: svn://svn.chromium.org/blink/trunk@184785 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sungmann.cho@navercorp.com authored
Review URL: https://codereview.chromium.org/697913002 git-svn-id: svn://svn.chromium.org/blink/trunk@184784 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
myid.o.shin@gmail.com authored
The handing of Enter key has moved from keydown to keypress in anchor element. And this makes behavior consistent with Firefox and IE. BUG=350738, 425859 R=pdr@chromium.org R=rob@robwu.nl TEST=LayoutTests/fast/events/press-enter-key-on-focused-element-inside-link.html Review URL: https://codereview.chromium.org/619613005 git-svn-id: svn://svn.chromium.org/blink/trunk@184783 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jfernandez@igalia.com authored
If the ‘width’ or ‘height’ (as appropriate) of the alignment subject is ‘auto’, its used value is the length necessary to make the alignment subject’s outer size as close to the size of the alignment container as possible, while still respecting the constraints imposed by ‘min/max-width/height’. Otherwise, this is equivalent to ‘start’. BUG=249451, 376823 Review URL: https://codereview.chromium.org/613273002 git-svn-id: svn://svn.chromium.org/blink/trunk@184782 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 02 Nov, 2014 4 commits
-
-
sigbjornf@opera.com authored
Following r184768, test no longer leaks. TBR=kouhei BUG=364417 NOTRY=true Review URL: https://codereview.chromium.org/696183002 git-svn-id: svn://svn.chromium.org/blink/trunk@184781 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
vsevik@chromium.org authored
TBR=aandrey NOTRY=true Review URL: https://codereview.chromium.org/694243002 git-svn-id: svn://svn.chromium.org/blink/trunk@184780 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rtakacs.u-szeged@partner.samsung.com authored
Final clean-up for methods with isSyncDatabase parameter. [1] https://codereview.chromium.org/660873004/ [2] https://codereview.chromium.org/666333002/ [3] THIS PATCH BUG=428254 Review URL: https://codereview.chromium.org/669063002 git-svn-id: svn://svn.chromium.org/blink/trunk@184779 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mlamouri@chromium.org authored
::didFail() is used instead of ::cancel() when a redirect failure happen. The same way ::didFail() is used when an access control failure happens. This is testing the change but also re-enables a test related to redirection. BUG=240912,429458 Review URL: https://codereview.chromium.org/689293003 git-svn-id: svn://svn.chromium.org/blink/trunk@184778 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 01 Nov, 2014 5 commits
-
-
amikhaylova@google.com authored
BUG=348919 Review URL: https://codereview.chromium.org/697833002 git-svn-id: svn://svn.chromium.org/blink/trunk@184775 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dongseong.hwang@intel.com authored
DrawingBuffer::paintCompositedResultsToCanvas()/copyToPlatformTexture() reuses the mailbox which was created for the compositor, instead of creating a temporary mailbox. It reduces mailbox creation as well as avoids context switching and glFlush. BUG=331181 Review URL: https://codereview.chromium.org/665073002 git-svn-id: svn://svn.chromium.org/blink/trunk@184774 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
robhogan@gmail.com authored
Revert of Use Shadow DOM to display fallback content for images (patchset #28 id:540001 of https://codereview.chromium.org/481753002/) Reason for revert: Broke accessibility tests on Chrome build Original issue's description: > This replaces the use of painting in RenderImage to display an image's alt text > with an implementation in shadow DOM. This initial implementation is close in > appearance to the legacy display of alt-text but will ultimately move closer to > the one seen in Firefox and described in http://hixie.ch/specs/alttext. > > The alt-text and broken-image icon is now rendered as: > > <style> > #alttext-container { > overflow: hidden; > border: 1px solid silver; > padding: 1px; > display: inline-block; > } > #alttext { display: none; overflow: hidden;} > </style> > <div id="alttext-container"> > <img src="data:png, [broken-image-icon]" width="16" height="16" align="left" style="margin: 0px"> > <div id="alt-text">Alt text in here</div> > </div> > > Some notes on the way the fallback content is now rendered: > > - The fallback content is rendered inside an inline-block so it does not calculate > its dimensions the way a replaced element (i.e. an image) would (as defined by > http://www.w3.org/TR/CSS2/visudet.html#inline-replaced-width). So where one of width > or height is auto but the other is not, the fallback content will not exactly match > the dimensions calculated by RenderImage in error mode currently. We do a modest > imitation of the logic in quirks mode, but in strict mode it will behave exactly like an inline-block. > > - Where the image has no src attribute and no alt attribute RenderImage.cpp > still looks after the painting of the element - no fallback content is generated > and no broken image is displayed. This is consistent with existing behaviour. > > - The only image resource requests that still use the synchronous load path are > those where the item is cached (and didn't error out), where it's a data: source, > where its the fallback image for an object element, or where it's the image > for a main resource load. All other image loads are now asynchronous so that > fallback content can be loaded outside the style recalc phase. > > > - Instead of aborting an image resource request when the src element is empty > (i.e. src='') we now allow the request to go through so that it can fail and > invoke the fallback content in HTMLImageLoader.cpp. > > - As you can see in the new result for fast/borders/rtl-border-05.html, since > the alt-text is displayed as an inline-block it no longer artificially shrinks > any border on the element to the broken-image icon. > > Some notes on the rebaselined test results: > > - I've modified inspector/network/network-image-404.html to output the state of > both the resource requests, i.e. the failed one and the resource request for the > data:png to display the broken image icon. > > - I've added a missing support file for fast/css/counters/complex-before.html - > its absence meant that the result was polluted by the behaviour of broken image > rendering. > > - Likewise for fast/images/imagemap-polygon* tests - our new rendering of failed > image loads was interfering with an assumption in the tests that a broken image > still painted a RenderImage. So I've removed the src attribute to allow the > assumption hold (img elements without a src attribute are painted by > RenderImage). > > - http/tests/security/local-image-from-remote-whitelisted.html has been masking > a bug - blink does not load the image even though it is whitelisted. I am > rebaselining the test to reflect the failure revealed by this CL and tracking > a fix under crbug.com/410949. > > - I have altered fast/forms/state-restore-to-non-edited-controls.html to wait > 100ms before submitting the form as the image load in the input element is now > asynchronous. > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=184770 TBR=esprehn@chromium.org NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/696123002 git-svn-id: svn://svn.chromium.org/blink/trunk@184773 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
lushnikov@chromium.org authored
Revert of [DevTools] Extract platform module. (patchset #4 id:40002 of https://codereview.chromium.org/673163004/) Reason for revert: This breaks DevTools at least in a hosted mode: the front-end does not load, exceptions are thrown from Runtime.js Original issue's description: > [DevTools] Extract platform module. > > BUG=none > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=184753 TBR=apavlov@chromium.org,pfeldman@chromium.org,vsevik@chromium.org,dgozman@chromium.org NOTREECHECKS=true NOTRY=true BUG=none Review URL: https://codereview.chromium.org/692343002 git-svn-id: svn://svn.chromium.org/blink/trunk@184772 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
robhogan@gmail.com authored
with an implementation in shadow DOM. This initial implementation is close in appearance to the legacy display of alt-text but will ultimately move closer to the one seen in Firefox and described in http://hixie.ch/specs/alttext. The alt-text and broken-image icon is now rendered as: <style> #alttext-container { overflow: hidden; border: 1px solid silver; padding: 1px; display: inline-block; } #alttext { display: none; overflow: hidden;} </style> <div id="alttext-container"> <img src="data:png, [broken-image-icon]" width="16" height="16" align="left" style="margin: 0px"> <div id="alt-text">Alt text in here</div> </div> Some notes on the way the fallback content is now rendered: - The fallback content is rendered inside an inline-block so it does not calculate its dimensions the way a replaced element (i.e. an image) would (as defined by http://www.w3.org/TR/CSS2/visudet.html#inline-replaced-width). So where one of width or height is auto but the other is not, the fallback content will not exactly match the dimensions calculated by RenderImage in error mode currently. We do a modest imitation of the logic in quirks mode, but in strict mode it will behave exactly like an inline-block. - Where the image has no src attribute and no alt attribute RenderImage.cpp still looks after the painting of the element - no fallback content is generated and no broken image is displayed. This is consistent with existing behaviour. - The only image resource requests that still use the synchronous load path are those where the item is cached (and didn't error out), where it's a data: source, where its the fallback image for an object element, or where it's the image for a main resource load. All other image loads are now asynchronous so that fallback content can be loaded outside the style recalc phase. - Instead of aborting an image resource request when the src element is empty (i.e. src='') we now allow the request to go through so that it can fail and invoke the fallback content in HTMLImageLoader.cpp. - As you can see in the new result for fast/borders/rtl-border-05.html, since the alt-text is displayed as an inline-block it no longer artificially shrinks any border on the element to the broken-image icon. Some notes on the rebaselined test results: - I've modified inspector/network/network-image-404.html to output the state of both the resource requests, i.e. the failed one and the resource request for the data:png to display the broken image icon. - I've added a missing support file for fast/css/counters/complex-before.html - its absence meant that the result was polluted by the behaviour of broken image rendering. - Likewise for fast/images/imagemap-polygon* tests - our new rendering of failed image loads was interfering with an assumption in the tests that a broken image still painted a RenderImage. So I've removed the src attribute to allow the assumption hold (img elements without a src attribute are painted by RenderImage). - http/tests/security/local-image-from-remote-whitelisted.html has been masking a bug - blink does not load the image even though it is whitelisted. I am rebaselining the test to reflect the failure revealed by this CL and tracking a fix under crbug.com/410949. - I have altered fast/forms/state-restore-to-non-edited-controls.html to wait 100ms before submitting the form as the image load in the input element is now asynchronous. Review URL: https://codereview.chromium.org/481753002 git-svn-id: svn://svn.chromium.org/blink/trunk@184770 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-