- 17 Oct, 2014 39 commits
-
-
rmcilroy@chromium.org authored
Modifies the idle time scheduling such that idle tasks which are posted during one idle period will not become pending until the next idle period. This enables idle tasks to repost themselves at the end of their execution without causing a flood of idle task execution in the remaining deadline period. BUG=421880 Review URL: https://codereview.chromium.org/640053003 git-svn-id: svn://svn.chromium.org/blink/trunk@183884 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
aberent@chromium.org authored
If a video is too narrow to display the full controls, including the cast button, on the control bar, then use an overlay cast button instead. BUG=423753 Review URL: https://codereview.chromium.org/658173002 git-svn-id: svn://svn.chromium.org/blink/trunk@183883 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
fs@opera.com authored
BUG=420022 Review URL: https://codereview.chromium.org/661643005 git-svn-id: svn://svn.chromium.org/blink/trunk@183882 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
lushnikov@chromium.org authored
As of today, the "format script" button is initialized as hidden and will update its state in response to editorSelected event. However, in case the event is sent prior to button construction, it should be initialized with current selected editor. BUG=424089 R=vsevik Review URL: https://codereview.chromium.org/658293003 git-svn-id: svn://svn.chromium.org/blink/trunk@183881 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
eustas@chromium.org authored
Settings checkbox UI state was changed from outside, that confused control. BUG=402406 Review URL: https://codereview.chromium.org/640633007 git-svn-id: svn://svn.chromium.org/blink/trunk@183880 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
timloh@chromium.org authored
When CSSPropertyParser::parseValue fails, we sometimes have already yielded property/value pairs (e.g. when parsing shorthands). In this case we roll back any yielded values. This patch moves the logic for this to CSSPropertyParser since this is a better fit for it and makes the parseValue interface more sensible. BUG=404023 Review URL: https://codereview.chromium.org/645033004 git-svn-id: svn://svn.chromium.org/blink/trunk@183879 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
horo@chromium.org authored
Chromium side fix is here: https://codereview.chromium.org/660973002 BUG=424464 Review URL: https://codereview.chromium.org/663723002 git-svn-id: svn://svn.chromium.org/blink/trunk@183878 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
eustas@chromium.org authored
Revert of Use count strings as keyframes/animation-name identifiers (patchset #2 id:20001 of https://codereview.chromium.org/651123003/) Reason for revert: Seems to cause crash: https://code.google.com/p/chromium/issues/detail?id=424520 Original issue's description: > Use count strings as keyframes/animation-name identifiers > > Strings are not valid keyframes/animation-name identifiers. This change > tracks the occurrence of these strings in the wild to provide data > on the impact dropping support for this would have. > > BUG=423424 > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=183856 TBR=timloh@chromium.org,dstockwell@chromium.org,alancutter@chromium.org NOTREECHECKS=true NOTRY=true BUG=423424 Review URL: https://codereview.chromium.org/666433002 git-svn-id: svn://svn.chromium.org/blink/trunk@183877 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rmcilroy@chromium.org authored
BUG=422841 TBR=eseidel Review URL: https://codereview.chromium.org/650103003 git-svn-id: svn://svn.chromium.org/blink/trunk@183876 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rune@opera.com authored
Start supporting style invalidation for selectors containing ::content, but still use SubtreeStyleChange on distributed children of the content element. If you have a selector ".class ::content .target", we will not invalidate the whole subtree for the element matching ".class", but do style invalidation for elements matching ".target". We will not cross the insertion point during invalidation at this point, but merely mark content elements found during style invalidation with SubtreeStyleChange. That may be done in a separate patch, but it requires the style invalidator to have invalidation sets scheduled for elements inside a shadow tree affect style invalidation of its host subtree. The addition of :host-context as boundary-crossing and insertion-point- crossing is in preparation for supporting style invalidation for the :host-context selector. This CL is split out of [1]. This CL relies on [2]. [1] https://codereview.chromium.org/639433002/ [2] https://codereview.chromium.org/637273003/ R=esprehn@chromium.org,chrishtr@chromium.org BUG=424123 Review URL: https://codereview.chromium.org/652223002 git-svn-id: svn://svn.chromium.org/blink/trunk@183875 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ajith.v@samsung.com authored
Editable element check is not taken care of disabled and readonly elements after getting the hittest result. Hence causing this issue. In this patch we are checking whether the element is readonly or disabled and not allowing paste popup to show. BUG= Review URL: https://codereview.chromium.org/246203004 git-svn-id: svn://svn.chromium.org/blink/trunk@183874 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
marja@chromium.org authored
... but use proper layering instead. PendingScript holds a Resource, and many places in the code are using both the PendingScript and the underlying Resource. For example, ScriptRunner holds a collection of PendingScripts, and ScriptLoaders then listen to the underlying Resources. This is confusing and error prone. The Resource - ScriptLoader - PendingScript - Element love quadrangle is messy in general. Both ScriptLoader and PendingScript refer to the Resource. The way to get ScriptLoader from PendingScript is via Element which PendingScript also holds. But there's no way to get PendingScript from ScriptLoader. This CL makes ScriptRunner access the ScriptLoaders directly and moves the PendingScript to ScriptLoader. In addition, it makes ScriptRunner not access the Resource of the ScriptLoader directly. This CL also cancels the hack from https://bugs.webkit.org/show_bug.cgi?id=92211 (r139942) where it was speculated that a crash can be caused by ScriptLoader getting the notifyFinished notification twice because it doesn't unsubscribe yet when it gets the first one. The speculative fix was to made it nullify ScriptLoader::m_resource and check for the nullity later. This is pretty surprising, since the obvious solution would've been to just unsubscribe early enough (which is done by this CL). Note a behavioral change: It's OK to call Resource::addClient even if the Resource is finished, and in that case, the client will be notified immediately. But PendingScript used to ASSERT that the Resource is not finished. This CL removes that restriction (the underlying Resource already handles adding clients to finished resources + made ScriptStreamer handle it too). Review URL: https://codereview.chromium.org/656113002 git-svn-id: svn://svn.chromium.org/blink/trunk@183873 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
hayato@chromium.org authored
Intend to replace the following typical for loop: for (Node* child = node.firstChild(); child; child = child->nextSibling()) { .... } with range-based for loop of C++11: for (Node& child : NodeTraversal::childrenOf(node)) { .... } Less verbose and improves readability, especially if we could close our eyes on NodeTraversal prefix. The following iterators are introduced to address common use cases in our code base: 1. NodeTraversal::childrenOf(const Node&) This could replace: for (Node* child = node.firstChild(); child; child = child->nextSibling()) { ... } with: for (Node& child : NodeTraversal::childrenOf(node)) { ... } 2. NodeTraversal::descendantsOf(const Node&) This could replace: for (Node* node = root.firstChild(); node; node = NodeTraversal::next(*node, &root) { ... } with: for (Node& node : NodeTraversal::descendantsOf(root)) { ... } 3. NodeTraversal::inclusiveDescendantsOf(const Node&) This could replace: for (Node* node = &root; node; node = NodeTraversal::next(*node, &root) { ... } with: for (Node& node : NodeTraversal::inclusiveDescendantsOf(root)) { ... } 4. NodeTraversal::fromNext(const Node&) This could replace: for (Node* node = NodeTraversal::next(start); node; node = NodeTraversal::next(*node) { ... } with: for (Node& node : NodeTraversal::fromNext(start)) { ... } There are also typed template versions for other element types: 5. Traversal<ElementType>::childrenOf(const Node&) This could replace: for (ElementType* child = Traversal<ElementType>::firstChild(node); child; child = Traversal<ElementType>::nextSibling(*child)) { ... } with: for (ElementType& child : Traversal<ElementType>::childrenOf(node)) { ... } 6. Traversal<ElementType>::descendantsOf(const Node&) This could replace: for (ElementType* node = Traversal<ElementType>::firstWithin(root); node; node = Traversal<ElementType>::next(*node, &root)) { ... } with: for (ElementType& node : Traversal<ElementType>::descendantsOf(root)) { ... } 7. Traversal<ElementType>::inclusiveDescendantsOf(const ElementType&) This could replace: for (ElementType* node = &root; node; node = Traversal<ElementType>::next(*node, &root)) { ... } with: for (ElementType& node : Traversal<ElementType>::inclusiveDescendantsOf(root)) { ... } 8. Traversal<ElementType>::fromNext(const Node&) This could replace: for (ElementType* node = Traversal<ElementType>::next(start); node; node = Traversal<ElementType>::next(*node) { ... } with: for (ElementType& node : Traversal<ElementType>::fromNext(start)) { ... } New iterators should be zero overhead because compilers can make them all inlined in a release build. As the first showcase, I let some files use this range-based for loops. This is not comprehensive so that this patch wouldn't get larger. Other changes will be done in another patch. We might want to have similar things for other classes, such as RenderObject, which can also be done in another patch. BUG=none TEST=no layout test failure Review URL: https://codereview.chromium.org/642973003 git-svn-id: svn://svn.chromium.org/blink/trunk@183872 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
hirono@chromium.org authored
We assume File instance has a file path if hasBackiingFile() is true. But previously the constructor for file system URL specifies true to the flag. This CL turns the flag to false at the constructor. BUG=NONE Review URL: https://codereview.chromium.org/660763004 git-svn-id: svn://svn.chromium.org/blink/trunk@183871 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
skobes@chromium.org authored
This was previously done in ScrollView::setScrollOffsetFromUpdateScrollbars but got lost with http://crrev.com/598093008. BUG=424042 Review URL: https://codereview.chromium.org/662733002 git-svn-id: svn://svn.chromium.org/blink/trunk@183870 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
Revert of DevTools: fix styles for glasspane (patchset #3 id:40001 of https://codereview.chromium.org/659043002/) Reason for revert: A better solution has been landed in https://src.chromium.org/viewvc/blink?view=rev&revision=183868 Original issue's description: > DevTools: fix styles for glasspane > > The glasspane should be a component-root so that it inherits all the > basic styling. > > R=pfeldman > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=183813 TBR=pfeldman@chromium.org,lushnikov@chromium.org NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/643773003 git-svn-id: svn://svn.chromium.org/blink/trunk@183869 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
R=pfeldman NOTRY=true Review URL: https://codereview.chromium.org/658303002 git-svn-id: svn://svn.chromium.org/blink/trunk@183868 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
loislo@chromium.org authored
We have to clear sessionId not only at the end but also after disconnecting frontend. Othervise it will be not null for the next devtools session and might be republished at navigation and break tracing session for the other tab. BUG= Review URL: https://codereview.chromium.org/657383002 git-svn-id: svn://svn.chromium.org/blink/trunk@183867 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
kenneth.r.christiansen@intel.com authored
Review URL: https://codereview.chromium.org/641963003 git-svn-id: svn://svn.chromium.org/blink/trunk@183865 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yurys@chromium.org authored
Added "Sampling" option on Timeline. When it is enabled we will stack JavaScript sampling profiler when Timeline is recorded and then will merge JS samples into Timeline events on the flame chart view. BUG=363976 Review URL: https://codereview.chromium.org/661023002 git-svn-id: svn://svn.chromium.org/blink/trunk@183864 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
kenneth.r.christiansen@intel.com authored
Review URL: https://codereview.chromium.org/658513003 git-svn-id: svn://svn.chromium.org/blink/trunk@183863 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
bartekn@chromium.org authored
Fix the issue where checking a form for :valid/:invalid would trigger invalid events for its elements (if set). BUG=360466 TEST=added a case to the layout test, to test for the issue Review URL: https://codereview.chromium.org/658063002 git-svn-id: svn://svn.chromium.org/blink/trunk@183862 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
haraken@chromium.org authored
This CL schedules an Oilpan's GC when a V8's major GC is triggered to avoid the following scenario: (1) A DOM object X holds a v8::Persistent to a V8 object. Assume that X is small but the V8 object is huge. (2) X's DOM wrapper is created. (3) The DOM wrapper becomes unreachable. (4) V8 triggers a GC. The V8's GC collects the DOM wrapper. However, X is not collected until a next Oilpan's GC is triggered. (5) If a lot of such DOM objects are created, we end up with a situation where V8's GC collects the DOM wrappers but the DOM objects are not collected forever. (Note that Oilpan's GC is not triggered unless Oilpan's heap gets full.) (6) V8 hits OOM. BUG=423047 Review URL: https://codereview.chromium.org/660753002 git-svn-id: svn://svn.chromium.org/blink/trunk@183861 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
kouhei@chromium.org authored
This CL moves SVGFitToViewBox hierarchy to parseAttributeNew. This is to replace the existing |SVGElement::parseAttribute| implementation, but as there are many callers, we would like to proceed this incrementally. a) Introduce |SVGElement::parseAttributeNew| *LANDED* b) Convert all overrides |SVGElement::parseAttribute| to a |parseAttributeNew| call. <-- This patch c) Replace existing |parseAttribute| with |parseAttributeNew|, and remove all overrides simply calling |parseAttributeNew| This patch is (b). BUG=397902 Review URL: https://codereview.chromium.org/651353004 git-svn-id: svn://svn.chromium.org/blink/trunk@183860 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tyoshino@chromium.org authored
We have RefPtr for preventing XHR from being destroyed in internalAbort(). But we're touching XHR's member variables in the caller of internalAbort(). We must have the RefPtr for protection there. BUG=421504 Review URL: https://codereview.chromium.org/663693003 git-svn-id: svn://svn.chromium.org/blink/trunk@183859 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yoav@yoav.ws authored
A false bug report led me to the realization that srcset's unit testing didn't include URLs with encoded spaces in them. Added such a test here. BUG=422914 Review URL: https://codereview.chromium.org/643703005 git-svn-id: svn://svn.chromium.org/blink/trunk@183858 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
timloh@chromium.org authored
The current parser allows an arbitrary number of %s (e.g. left: 10%%%), but we shouldn't depend on it in our unit tests. Review URL: https://codereview.chromium.org/641343004 git-svn-id: svn://svn.chromium.org/blink/trunk@183857 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
alancutter@chromium.org authored
Strings are not valid keyframes/animation-name identifiers. This change tracks the occurrence of these strings in the wild to provide data on the impact dropping support for this would have. BUG=423424 Review URL: https://codereview.chromium.org/651123003 git-svn-id: svn://svn.chromium.org/blink/trunk@183856 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
bashi@chromium.org authored
Before this CL, we allocate memory for IDL dictionaries each time we use them. For performance sensitive methods, this may not be acceptable. Avoid allocating them in the oilpan heap. Instead, put them on stack. Dictionaries can be a member of collections, so we use ALLOW_ONLY_INLINE_ALLOCATION(). Side effect of this change: If an impl class implements an IDL method which returns a dictionary, the impl method needs to take an argument for return value. This CL also add blank lines in generated dictionary impl classes for readability. BUG=321462 Review URL: https://codereview.chromium.org/656073002 git-svn-id: svn://svn.chromium.org/blink/trunk@183855 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rob.buis@samsung.com authored
The AffineTransformation for animateMotion is pretty rare and just makes SVGGraphicsElement take up more memory, so move it to SVGElementRareData. Review URL: https://codereview.chromium.org/660653004 git-svn-id: svn://svn.chromium.org/blink/trunk@183854 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
leviw@chromium.org authored
The code to cache preferredMainAxisContentExtentForChild when possible and re-use to avoid forcing layout was broken in the case that a child's flex basis changed to cause it to be dependent on layout, triggering an assert in debug. Just pushing it down the normal path fixes the issue. BUG=366185 Review URL: https://codereview.chromium.org/655053002 git-svn-id: svn://svn.chromium.org/blink/trunk@183853 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
haraken@chromium.org authored
TBR=sof@opera.com Review URL: https://codereview.chromium.org/656403002 git-svn-id: svn://svn.chromium.org/blink/trunk@183852 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ccameron@chromium.org authored
The scrollCount field is unused. The unacceleratedScrollingDeltaX/Y field always equal deltaX/Y (by inspection, then by adding an assert and testing), so use those directly. BUG=133097 Review URL: https://codereview.chromium.org/658953003 git-svn-id: svn://svn.chromium.org/blink/trunk@183851 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
navabi@google.com authored
Currently, chromium hung bots and blink hung bots are shown in their corresponding views. With this change, all hung bots will show up in the Trooper view. This includes the chromium and blink ones, but also others other trees (e.g. non-closers). BUG=412189 Review URL: https://codereview.chromium.org/661463004 git-svn-id: svn://svn.chromium.org/blink/trunk@183850 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yhirano@chromium.org authored
We are about to support Promise<T> syntax in the Web IDL parser. As it is specified in the Web IDL spec, I would like to implement it in tools/idl_parser. This CL is a preparation for the change in chromium side, in order not to break the existing behavior when the change lands. BUG=421539 Review URL: https://codereview.chromium.org/654193002 git-svn-id: svn://svn.chromium.org/blink/trunk@183849 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
chrishtr@chromium.org authored
BUG=423071 Review URL: https://codereview.chromium.org/653303003 git-svn-id: svn://svn.chromium.org/blink/trunk@183848 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
samli@chromium.org authored
Add a new hidden devtools experiment for animation inspection within the inspector. A new inspector domain is created for Animations. CSS Animations, CSS Transitions and Web Animations can be viewed in an Animations pane when an animation is in effect and targeting the element being viewed in the Elements pane. Each animation can be paused, played and scrubbed based on time position. Animation properties are shown for all animations. BUG=419269 Review URL: https://codereview.chromium.org/620783002 git-svn-id: svn://svn.chromium.org/blink/trunk@183847 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
fmalita@chromium.org authored
(only used in unit tests) R=schenney@chromium.org,senorblanco@chromium.org Review URL: https://codereview.chromium.org/657293004 git-svn-id: svn://svn.chromium.org/blink/trunk@183846 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sergiyb@chromium.org authored
Alerts history will return a list of IDs, which can then be used to get actual alerts from history. This allows to avoid exceeding memory and response size limits when processing the query. BUG=416182 R=ojan@chromium.org Review URL: https://codereview.chromium.org/664563002 git-svn-id: svn://svn.chromium.org/blink/trunk@183845 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 16 Oct, 2014 1 commit
-
-
rune@opera.com authored
When crossing an insertion point boundary from style recalc, we mark the distributed nodes for subtree style recalc. The reason is that the distributed nodes will have their style recalculated in the context of where they are distributed from. In the case below, changing class=a on content will affect the style of class=b. The invalidation starts on class=a and will not reach class=b in the invalidation traversal. The bug was that InsertionPoint::willRecalcStyle had an early return if the parent style change was at least an Inherit, but that is not the case if the class change does not affect anything at, or above, the insertion point, like in the case below. <div> <:shadow-root> <style>.a::content .b { ... }</style> <content class="a"></content> </:shadow-root> <div class="b"></div> </div> R=esprehn@chromium.org,chrishtr@chromium.org BUG=423293 Review URL: https://codereview.chromium.org/637273003 git-svn-id: svn://svn.chromium.org/blink/trunk@183844 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-