- 03 Mar, 2014 26 commits
-
-
pfeldman@chromium.org authored
R=caseq@chromium.org Review URL: https://codereview.chromium.org/185333002 git-svn-id: svn://svn.chromium.org/blink/trunk@168285 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pfeldman@chromium.org authored
R=caseq@chromium.org Review URL: https://codereview.chromium.org/185323002 git-svn-id: svn://svn.chromium.org/blink/trunk@168284 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
Revert of Don't setStyle the RenderView every style recalc (https://codereview.chromium.org/185263002/) Reason for revert: Crash-broke fast/images/link-body-content-imageDimensionChanged-crash.html on "WebKit Android (Nexus 4)" Original issue's description: > Don't setStyle the RenderView every style recalc > > Prior to this CL, we were setting the style of the RenderView on every style > recalc because we were comparing the RenderView's overflow style with the wrong > value. This CL corrects the bug. > > This CL doesn't have much effect yet, but it will become important in a future > CL when we use style modification on RenderLayers to scope compositing updates. > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=168254 TBR=eseidel@chromium.org,esprehn@chromium.org,ojan@chromium.org,abarth@chromium.org NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/183883009 git-svn-id: svn://svn.chromium.org/blink/trunk@168283 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pfeldman@chromium.org authored
R=caseq@chromium.org Review URL: https://codereview.chromium.org/185233002 git-svn-id: svn://svn.chromium.org/blink/trunk@168282 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pfeldman@chromium.org authored
R=caseq@chromium.org Review URL: https://codereview.chromium.org/184823002 git-svn-id: svn://svn.chromium.org/blink/trunk@168281 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jinho.bang@samsung.com authored
Added null and invalid argument test cases. Review URL: https://codereview.chromium.org/179493002 git-svn-id: svn://svn.chromium.org/blink/trunk@168280 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=167551 BUG=344774 TBR=jamesr@chromium.org Review URL: https://codereview.chromium.org/185553004 git-svn-id: svn://svn.chromium.org/blink/trunk@168279 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
a.bah@samsung.com authored
In applyInlineStyleToNodeRange(), a call to removeConflictingInlineStyleFromRun() can modify the start and end Nodes of InlineRunToApplyStyle. For the crash scenario, the start node being set in removeConflictingInlineStyleFromRun() is invalid and further use of it when calling positionToComputeInlineStyleChange() causes a crash. Thus adding a check for startAndEndAreStillInDocument() fixes the crash. However, since for the invalid scenario positionForStyleComputation shall not be set, we should check for it's validity before using the same for creating the StyleChange object. Have added a testcase based on the simplified clusterfuzz testcase added by yoichio in http://crbug.com/343799 which verifies the crash. BUG=343799 Review URL: https://codereview.chromium.org/181103004 git-svn-id: svn://svn.chromium.org/blink/trunk@168278 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
kouhei@chromium.org authored
BUG= Review URL: https://codereview.chromium.org/185673002 git-svn-id: svn://svn.chromium.org/blink/trunk@168277 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=168245 BUG=114658 TBR=dongseong.hwang@intel.com Review URL: https://codereview.chromium.org/185533003 git-svn-id: svn://svn.chromium.org/blink/trunk@168273 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mkwst@chromium.org authored
R=jochen@chromium.org Review URL: https://codereview.chromium.org/184543002 git-svn-id: svn://svn.chromium.org/blink/trunk@168272 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tasak@google.com authored
BUG=348401 TEST=fast/css/use-incorrect-svg-crash.html TBR=morrita@chromium.org, dglazkov@chromium.org Review URL: https://codereview.chromium.org/183743012 git-svn-id: svn://svn.chromium.org/blink/trunk@168271 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=168245 BUG=114658 TBR=dongseong.hwang@intel.com Review URL: https://codereview.chromium.org/183833008 git-svn-id: svn://svn.chromium.org/blink/trunk@168270 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yurys@chromium.org authored
BUG=None R=loislo@chromium.org Review URL: https://codereview.chromium.org/176883013 git-svn-id: svn://svn.chromium.org/blink/trunk@168268 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=167551 BUG=344774 TBR=jamesr@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/183693005 git-svn-id: svn://svn.chromium.org/blink/trunk@168267 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
This patch also allows multiple bugs on the BUG= line, perhaps having some non-digit characters (see r168027 for an example). It also occurred to me that with this patch committed, we should require that BUG= (and R=) starts at the beginning of line NOTRY=true Review URL: https://codereview.chromium.org/177123013 git-svn-id: svn://svn.chromium.org/blink/trunk@168266 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
caseq@chromium.org authored
BUG= R=pfeldman@chromium.org Review URL: https://codereview.chromium.org/184043004 git-svn-id: svn://svn.chromium.org/blink/trunk@168265 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
nbarth@chromium.org authored
InterfaceDependencies.txt was used by Perl. This is no longer necessary in Python, as we pickle (which is faster and avoids having ad hoc reading/writing). R=haraken BUG=341748 Review URL: https://codereview.chromium.org/180273009 git-svn-id: svn://svn.chromium.org/blink/trunk@168264 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dstockwell@chromium.org authored
This was removed from the spec [1] in favor of endDelay. [1] https://github.com/web-animations/web-animations-spec/commit/d00254dd8a79ae5f06b3db144f37302bda4f69ce NOTRY=true BUG=335350 Review URL: https://codereview.chromium.org/180163003 git-svn-id: svn://svn.chromium.org/blink/trunk@168263 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
shans@chromium.org authored
This patch introduces the InterpolableValue hierarchy, which stores the interpolable portion of generic values. This is part of an effort to refactor the animations pipeline in order to make it generic on animation value type (see linked master bug). This header is not yet included anywhere. It will be used in future patches. BUG=346495 Review URL: https://codereview.chromium.org/177183007 git-svn-id: svn://svn.chromium.org/blink/trunk@168262 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dstockwell@chromium.org authored
BUG=335350 Review URL: https://codereview.chromium.org/178663007 git-svn-id: svn://svn.chromium.org/blink/trunk@168261 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
haraken@chromium.org authored
(Background: This is a preparation CL for making DOMWrapperWorld::current() callable from anywhere.) Currently, when we initialize a context, we need to call the following things in a proper order. - V8PerContextDataHolder::install() - V8PerContextData::create() - V8PerContextData::init() - gin::ContextHolder() - gin::ContextHolder::SetContext() However, this is more complicated than necessary. This CL refactors code so that we just need to call V8PerContextData::create() when initializing a context. Specifically, this CL does the following refactoring: - Move gin::ContextHolder from V8WindowShell/WorkerScriptController to V8PerContextData. - Remove V8_STORE_PRIMORDIAL macro. - Move the contents of V8PerContextData::init() to V8PerContextData's constructor. BUG=341032 Review URL: https://codereview.chromium.org/180773003 git-svn-id: svn://svn.chromium.org/blink/trunk@168260 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
nbarth@chromium.org authored
Followup to: Kill [SetWrapperReferenceFromReference] IDL extended attribute https://codereview.chromium.org/181513002/ TBR=haraken BUG=345503 Review URL: https://codereview.chromium.org/176993007 git-svn-id: svn://svn.chromium.org/blink/trunk@168259 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ksakamoto@chromium.org authored
When a font resource takes a long time to download, currently Blink keeps the text invisible until the font is ready. After this patch, Blink behaves similar to FireFox; keeps the text invisible until 3 seconds, then fallback to the next available font in the fallback list. When the webfont finally loads, change the text to use it. - Add a Timer to FontResource that fires after 3 seconds since load start. - fontLoadWaitLimitExceeded() callback invalidates the fallback font and triggers style recalc. - Fallback fonts have m_skipDrawing boolean in CustomFontData, that is false if the font load exceeds the wait limit. - FontFallbackList::shouldSkipDrawing() returns true if it contains at least one FontData with m_skipDrawing == true. BUG=235303 TEST=http/tests/webfont/slow-loading.html Review URL: https://codereview.chromium.org/171823002 git-svn-id: svn://svn.chromium.org/blink/trunk@168258 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
kouhei@chromium.org authored
BUG=None Review URL: https://codereview.chromium.org/171743004 git-svn-id: svn://svn.chromium.org/blink/trunk@168257 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dcheng@chromium.org authored
Right now, this can return true even if the frame is detached, since it doesn't check that the frame has a non-null host. The remaining changes in DOMWindow are to preserve current web visible behavior, as well as fixing a null pointer dereferences that this exposes in Performance and ScreenOrientation. BUG=347331 R=abarth@chromium.org Review URL: https://codereview.chromium.org/131113003 git-svn-id: svn://svn.chromium.org/blink/trunk@168256 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 02 Mar, 2014 5 commits
-
-
dpranke@chromium.org authored
These will need baselines too, most likely. TBR=scottmg@chromium.org BUG=309197 Review URL: https://codereview.chromium.org/185303004 git-svn-id: svn://svn.chromium.org/blink/trunk@168255 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
Prior to this CL, we were setting the style of the RenderView on every style recalc because we were comparing the RenderView's overflow style with the wrong value. This CL corrects the bug. This CL doesn't have much effect yet, but it will become important in a future CL when we use style modification on RenderLayers to scope compositing updates. Review URL: https://codereview.chromium.org/185263002 git-svn-id: svn://svn.chromium.org/blink/trunk@168254 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pdr@chromium.org authored
This patch fixes a crash on xe.com where the text autosizer would call isEmpty() on a RenderObject and crash. The issue is that RenderSVGShape overrides RenderObject::isEmpty and implements it differently: RenderObject::isEmpty() - true if the RenderObject has children RenderSVGShape::isEmpty() - true if the bounding box is empty I've refactored RenderSVGShape::isEmpty() as isShapeEmpty() to both clarify the override and fix a crash. BUG=302005 NOTRY=true Review URL: https://codereview.chromium.org/185243002 git-svn-id: svn://svn.chromium.org/blink/trunk@168252 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dpranke@chromium.org authored
Normally if run-webkit-tests detects regressions, it returns the number of regressions in the exit code (i.e., if 5 tests fail, the exit code is 5). We also use a few magic values to indicate other errors (like 130 for interrupted, -1/254 for internal error, etc.). This means that if we get a lot of errors, we can overlap and produce confusing results. This change adds a range check on the number of errors; if we get more than 101 failures, we limit the exit code to 101. This should prevent overlap while preserving behavior in all but very abnormal circumstances. Arguably a better change would just be to use 1 for the error and ignore the number of failures altogether, but that might break scripts so I'm not going to do this now. TBR=scottmg@chromium.org BUG=309197 Review URL: https://codereview.chromium.org/185503002 git-svn-id: svn://svn.chromium.org/blink/trunk@168251 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dpranke@chromium.org authored
This change suppresses the remaining failures resulting from the switch to Visual Studio 2013 until scottmg or I can go through and rebaseline them. There's probably a couple local failures from my machine that shouldn't be rebaselined, and a couple of legit bugs as well, which is why I don't want to use 'NeedsRebaseline' for the bot to automatically deal with this. TBR=scottmg@chromium.org BUG=309197 Review URL: https://codereview.chromium.org/183973012 git-svn-id: svn://svn.chromium.org/blink/trunk@168250 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 01 Mar, 2014 9 commits
-
-
abarth@chromium.org authored
TBR=esprehn@chromium.org Review URL: https://codereview.chromium.org/185273002 git-svn-id: svn://svn.chromium.org/blink/trunk@168248 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sigbjornf@opera.com authored
Prefer this helper function when throwing TypeErrors. R= BUG= Review URL: https://codereview.chromium.org/183253003 git-svn-id: svn://svn.chromium.org/blink/trunk@168247 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sigbjornf@opera.com authored
indexeddb is available in Worker contexts, including this event. R= BUG=340522 Review URL: https://codereview.chromium.org/185323003 git-svn-id: svn://svn.chromium.org/blink/trunk@168246 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dongseong.hwang@intel.com authored
Rationale 1. GraphicsLayer deals with background-color layer as a contents layer, so a background-color layer is in trouble in terms of the correct order with negative z-order children. 2. CompositedLayerMapping has the big hack to decide the given layer can be background-color layer. Unfortunately, the big hack is incomplete and invasive. 3. Hybrid Accelerated Rasterization will cover this optimization in more generic way. 4. background-color layer covers very limited cases. A layer-promoted box object must not have children, not have decoration, only have a background-color property. BUG=114658, 340691 TEST=compositing/background-color/background-color-drawn-over-child.html, compositing/* Review URL: https://codereview.chromium.org/178013003 git-svn-id: svn://svn.chromium.org/blink/trunk@168245 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
This CL moves some code relating to walking the RenderLayer tree and updating GraphicsLayers out of RenderLayerCompositor. This code didn't interact with any of the state in RenderLayerCompositor, so it's easy to untangle. I've also taken the opportunity to remove a pretty gross hack using static variables to communicate data across the recursive tree walk. Now we just use normal member variables in the stack object that manages the tree walk. This CL shouldn't change any behavior. Review URL: https://codereview.chromium.org/185293002 git-svn-id: svn://svn.chromium.org/blink/trunk@168244 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dominikg@chromium.org authored
Revert of Use SkLayerDrawLooper::Builder to construct SkLayerDrawLooper. (https://codereview.chromium.org/177473003/) Reason for revert: crash in SkCanvas::getTotalMatrix (crbug.com/348122) Reverting this to see if it fixes it, otherwise we can reland. Original issue's description: > Use SkLayerDrawLooper::Builder to construct SkLayerDrawLooper. > > The addLayer() methods of SkLayerDrawLooper will soon be removed. This CL > updates all uses of those methods with the corresponding methods in > SkLayerDrawLooper::Builder. > > BUG=skia:2141 > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=168041 TBR=schenney@chromium.org,jbroman@chromium.org NOTREECHECKS=true NOTRY=true BUG=skia:2141 Review URL: https://codereview.chromium.org/178113003 git-svn-id: svn://svn.chromium.org/blink/trunk@168243 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
abarth@chromium.org authored
The only reason we had a HashMap in the overlap map was to handle a recursive treewalk in the case where we need to be composited because of our children. It turns out the HashMap was wrong in the case where those children got composited into another non-root layer. In that case, they would already be in the overlap map and would be excluded in the recursive walk. This CL removes the HashMap and instead just unites the bounds of all the children during the normal recusive walk. If we need to composite ourself because of our decendants, we use the united rect instead of recursively adding all the descendant rects individually. This is both faster (3% on the toggle_drawer compositing update) and more correct (see test). R=enne@chromium.org Review URL: https://codereview.chromium.org/178313004 git-svn-id: svn://svn.chromium.org/blink/trunk@168242 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yoav@yoav.ws authored
Two problems with the current srcset parsing algorithm are fixed here: 1. When a set of descriptors contained only invalid descriptors, the resource wasn't ignored. 2. When more than 1 resource shared a single DPR value, the last one was taken into account, rather than the first one. I've also added test and fixed current ones to prevent this from regressing in the future. BUG=347998 Review URL: https://codereview.chromium.org/184523003 git-svn-id: svn://svn.chromium.org/blink/trunk@168241 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sigbjornf@opera.com authored
CloseEvent and XMLHttpRequestProgressEvent are also exposed inside Workers. R= BUG=340522 Review URL: https://codereview.chromium.org/178193014 git-svn-id: svn://svn.chromium.org/blink/trunk@168240 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-