- 07 Jun, 2014 15 commits
-
-
jchaffraix@chromium.org authored
Chromium's checkdeps.py has moved but the script was never updated. TEST=Manually run the script and it works! Review URL: https://codereview.chromium.org/325473003 git-svn-id: svn://svn.chromium.org/blink/trunk@175733 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
esprehn@chromium.org authored
To avoid needing put all the children into a NodeVector inside removeChildren() we can reverse the order of childrenChanged and the associated child notifications (insertedInto/removedFrom). This seems fine, it means that a parent now is not told it has new children until they've already been told they're in the tree. Inversely it does mean that when a child is told it's in the tree the parent doesn't know it has new children yet, but that's less crazy since it doesn't result in things like children without inDocument() bits being set existing inside ::childrenChanged. For removal I swapped the calls to notifyNodeRemoved with the calls to childrenChanged. For insertion I moved the call to childrenChanged into the notifyNodeInserted function. This is necessary since it can run script and we need to call childrenChanged before running the script. I also added some more RefPtr<Node> protect(this) guards to methods which can runs script and more ScriptForbiddenScopes to parts of the code that now can't run script. Review URL: https://codereview.chromium.org/306233005 git-svn-id: svn://svn.chromium.org/blink/trunk@175732 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
GraphicsLayerUpdater::rebuildTree and GraphicsLayerUpdater::update no longer have anything to do with each other. This CL move rebuildTree into a separate file, called GraphicsLayerTreeBuilder. Review URL: https://codereview.chromium.org/319183006 git-svn-id: svn://svn.chromium.org/blink/trunk@175731 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
We don't appear to need this incremental update anymore. BUG=343756 Review URL: https://codereview.chromium.org/317373004 git-svn-id: svn://svn.chromium.org/blink/trunk@175730 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
This CL teaches the callers of CompositingUpdateOnScroll how to do partial compositing updates. Now that they're smarter, we can use CompositingUpdateAfterCompositingInputChange and we don't need CompositingUpdateOnScroll anymore. Review URL: https://codereview.chromium.org/326443002 git-svn-id: svn://svn.chromium.org/blink/trunk@175729 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
c.shu@samsung.com authored
BUG=380054 Review URL: https://codereview.chromium.org/325483002 git-svn-id: svn://svn.chromium.org/blink/trunk@175728 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pdr@chromium.org authored
This patch fixes the deleteSelection callsites in CompositeEditCommand after [1] refactored them to remove the bool 'replace' parameter. [1] http://src.chromium.org/viewvc/blink?revision=164025&view=revision BUG=381069 Review URL: https://codereview.chromium.org/321583004 git-svn-id: svn://svn.chromium.org/blink/trunk@175727 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rbyers@chromium.org authored
Previously TouchEvents had their co-ordinates truncated to integers. By supporting sup-pixel precision we get smoother dragging and line drawing at slow speeds on high-dpi devices or when zoomed. Intent to ship thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/J0Lca9fCuNw Tests depend on EventSender change here: https://src.chromium.org/viewvc/chrome?view=rev&revision=275340 BUG=323935 Review URL: https://codereview.chromium.org/298133003 git-svn-id: svn://svn.chromium.org/blink/trunk@175726 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
enne@chromium.org authored
These have been removed in Chrome and do nothing. R=jochen@chromium.org BUG=none Review URL: https://codereview.chromium.org/298803009 git-svn-id: svn://svn.chromium.org/blink/trunk@175725 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jbroman@chromium.org authored
We haven't supported Core Graphics in some time. Only one of these functions is implemented at all, and it is unused. BUG=381789 Review URL: https://codereview.chromium.org/315403007 git-svn-id: svn://svn.chromium.org/blink/trunk@175724 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
srirama.m@samsung.com authored
BUG=350571 Review URL: https://codereview.chromium.org/318923004 git-svn-id: svn://svn.chromium.org/blink/trunk@175723 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ch.dumez@samsung.com authored
Use ElementTraversal API in ContainerNode::checkForChildrenAdjacentRuleChanges() as we are only interested in child Elements. R=esprehn@chromium.org Review URL: https://codereview.chromium.org/316173007 git-svn-id: svn://svn.chromium.org/blink/trunk@175722 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=175704 TBR=abarth@chromium.org Review URL: https://codereview.chromium.org/311393004 git-svn-id: svn://svn.chromium.org/blink/trunk@175721 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
kochi@chromium.org authored
Removes <style scoped>. This was discussed and approved with LGTMs in blink-dev: https://groups.google.com/a/chromium.org/d/msg/blink-dev/R1x18ZLS5qQ/Bjuh_cENhlQJ Chrome status dashboard entry: http://www.chromestatus.com/features/5374137958662144 Note: this is based on esprehn's original cl: https://codereview.chromium.org/214693002/ BUG=379096 TEST=pass all layout tests Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175555 Review URL: https://codereview.chromium.org/310443002 git-svn-id: svn://svn.chromium.org/blink/trunk@175720 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
leviw@chromium.org authored
Blink r175423 fixed non-composited nested RenderView repainting for repaint-after-layout, but in the process broke repainting of composited nested RenderViews for all code paths. The fix is to correctly issue repaints to the backing store of composited RenderViews regardless of whether they're nested. BUG=381022 R=esprehn@chromium.org Review URL: https://codereview.chromium.org/318183002 git-svn-id: svn://svn.chromium.org/blink/trunk@175718 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 06 Jun, 2014 25 commits
-
-
ojan@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=175702 BUG=369375 TBR=dcheng@chromium.org Review URL: https://codereview.chromium.org/321613003 git-svn-id: svn://svn.chromium.org/blink/trunk@175717 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
This call isn't need anymore. Now setNeedsToUpdateAncestorDependentProperties does this work. BUG=332248 Review URL: https://codereview.chromium.org/319863004 git-svn-id: svn://svn.chromium.org/blink/trunk@175716 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
Revert of Implementing mixed content for forms posting to insecure location from secure ones (https://codereview.chromium.org/311033003/) Reason for revert: This CL incorrectly integrates with the inspector. Notice that in Element::didModifyAttribute, InspectorInstrumentation::didModifyDOMAttr will be called with the original value, not the mutated value. Original issue's description: > Implementing mixed content for forms posting to insecure location from secure ones. > > When a form "action" attribute is pointing to insecure location from a secure one, this is flagged as mixed content. This is even checked if the pages dynamically changes the "action" attribute after the initial loading. The mixed content is non-blocking by default, however, this can be overridden in the preferences, and this will cause a submit to silently fail, other than a console message. > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175714 TBR=jww@chromium.org,mkwst@chromium.org,mohammed@chromium.org NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/319183008 git-svn-id: svn://svn.chromium.org/blink/trunk@175715 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mohammed@chromium.org authored
When a form "action" attribute is pointing to insecure location from a secure one, this is flagged as mixed content. This is even checked if the pages dynamically changes the "action" attribute after the initial loading. The mixed content is non-blocking by default, however, this can be overridden in the preferences, and this will cause a submit to silently fail, other than a console message. Review URL: https://codereview.chromium.org/311033003 git-svn-id: svn://svn.chromium.org/blink/trunk@175714 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
acolwell@chromium.org authored
> Eliminate MediaPlayer & MediaPlayerClient abstractions(play/pause, other APIs) > > BUG=350571 > > Review URL: https://codereview.chromium.org/298093004 TBR=srirama.m@samsung.com Review URL: https://codereview.chromium.org/325513002 git-svn-id: svn://svn.chromium.org/blink/trunk@175713 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
acolwell@chromium.org authored
> Eliminate MediaPlayer & MediaPlayerClient abstractions(seek, duration, poster APIs) > > Bug=350571 > > Review URL: https://codereview.chromium.org/306123003 TBR=srirama.m@samsung.com Review URL: https://codereview.chromium.org/314413003 git-svn-id: svn://svn.chromium.org/blink/trunk@175712 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
acolwell@chromium.org authored
> Eliminate MediaPlayer & MediaPlayerClient abstractions(rate, setRate and other APIs) > > BUG=350571 > > Chromium side patch for this is https://codereview.chromium.org/303403002/ > > Review URL: https://codereview.chromium.org/304353005 TBR=srirama.m@samsung.com Review URL: https://codereview.chromium.org/320053003 git-svn-id: svn://svn.chromium.org/blink/trunk@175711 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
amikhaylova@google.com authored
BUG=376194 Review URL: https://codereview.chromium.org/312143003 git-svn-id: svn://svn.chromium.org/blink/trunk@175709 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
There's no connection between being visible and z-order lists. There's no reason to mark the z-order list as dirty when changing visibility status. Review URL: https://codereview.chromium.org/320593004 git-svn-id: svn://svn.chromium.org/blink/trunk@175708 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=175681 BUG=313438 TBR=rob.buis@samsung.com Review URL: https://codereview.chromium.org/311193011 git-svn-id: svn://svn.chromium.org/blink/trunk@175707 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dcheng@chromium.org authored
The previous version of this test generated non-deterministic results due to the way console messages are generated. Specifically, the test case was constructed while parsing might not yet be complete, but the act of constructing the test case generated console messages. If a console message is generated with no specified line number, Document::internalAddMessage attempts to attach a line number, but one of the conditionals for doing so is whether the Document is still parsing making the output non-deterministic. To get around that, the test has been rewritten to only run once the document is finished loading. BUG=381451 R=japhet@chromium.org Review URL: https://codereview.chromium.org/314393002 git-svn-id: svn://svn.chromium.org/blink/trunk@175706 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
This code evolved and grew over the years, but it seems to be trying to compute something very simple. Review URL: https://codereview.chromium.org/307933010 git-svn-id: svn://svn.chromium.org/blink/trunk@175704 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dcheng@chromium.org authored
BUG=369375 TBR=sandersd@chromium.org Review URL: https://codereview.chromium.org/321603002 git-svn-id: svn://svn.chromium.org/blink/trunk@175702 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dcheng@chromium.org authored
TBR=falken@chromium.org Review URL: https://codereview.chromium.org/319233002 git-svn-id: svn://svn.chromium.org/blink/trunk@175701 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ajuma@chromium.org authored
This allows expanding the GPU rasterization trigger for a field trial. The expanded trigger is <meta name="viewport" content="width=device-width, minimum-scale=1.0"> BUG=380454 Review URL: https://codereview.chromium.org/309593007 git-svn-id: svn://svn.chromium.org/blink/trunk@175699 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
eae@chromium.org authored
Fix bug in Element::scrollWidth/scrollHeight where the scroll offset was truncated to an integer value before being adjusted for zoom. TEST=fast/sub-pixel/clientwidth-matches-scrollwidth-for-float.html BUG=381039 Review URL: https://codereview.chromium.org/319633004 git-svn-id: svn://svn.chromium.org/blink/trunk@175698 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jbroman@chromium.org authored
This is simpler, and marginally more efficient (as it avoids setting up the paint in a default state only to immediately overwrite it). GraphicsContext::setupShader is declared but never defined, so its declaration has been removed while here. BUG=381750 Review URL: https://codereview.chromium.org/311193009 git-svn-id: svn://svn.chromium.org/blink/trunk@175697 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mkosiba@chromium.org authored
Looks like after Blink r175269 the moment where the test runner grabs the text dump may occur after the quick-fail timer. I've only been able to repro it once out of about 40 invocations so I can only speculate that the navigation which we cancel in beforeunload is somethimes delaying the test's completion long enough for the deadman's switch to fire. Since the order of events is correct even in the failing case it's relatively simple to make the test pass regardless of whether the test runner grabs the text dump before or after the timer fires. BUG=380151 Review URL: https://codereview.chromium.org/319673002 git-svn-id: svn://svn.chromium.org/blink/trunk@175696 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
falken@chromium.org authored
BUG=381827 TBR=jsbell NOTRY=true Review URL: https://codereview.chromium.org/314413002 git-svn-id: svn://svn.chromium.org/blink/trunk@175695 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
CompositingUpdateAfterStyleChange does the same thing as CompositingUpdateAfterCompositingInputChange. There's no reason to have two enums. Also, I've inlined FrameView::updateCompositingLayersAfterStyleChange because that function just contained a redundant null check. BUG=332248 Review URL: https://codereview.chromium.org/321573002 git-svn-id: svn://svn.chromium.org/blink/trunk@175694 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
falken@chromium.org authored
BUG=381827 TBR=jsbell Review URL: https://codereview.chromium.org/314413002 git-svn-id: svn://svn.chromium.org/blink/trunk@175693 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ajuma@chromium.org authored
This makes CompositingReasonFinder::requiresCompositingForAnimation take a RenderStyle* rather than a RenderObject*. Review URL: https://codereview.chromium.org/317013005 git-svn-id: svn://svn.chromium.org/blink/trunk@175692 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
This function was written in a confusing way. R=ojan@chromium.org Review URL: https://codereview.chromium.org/324513003 git-svn-id: svn://svn.chromium.org/blink/trunk@175691 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
alokp@chromium.org authored
The hint is now per page instead of per layer. BUG=367202 Review URL: https://codereview.chromium.org/312203002 git-svn-id: svn://svn.chromium.org/blink/trunk@175690 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sanjoy.pal@samsung.com authored
BUG=None Review URL: https://codereview.chromium.org/311263009 git-svn-id: svn://svn.chromium.org/blink/trunk@175689 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-