- 27 Mar, 2014 40 commits
-
-
ager@chromium.org authored
We were missing the xcode_settings OTHER_CFLAGS. R=oilpan-reviews@chromium.org, tkent@chromium.org, zerny@chromium.org BUG= Review URL: https://codereview.chromium.org/214403002 git-svn-id: svn://svn.chromium.org/blink/trunk@170222 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dsinclair@chromium.org authored
When the background of the table row is changed we repaint the entire table. This CL adds a layout test showing the issue. BUG=357291 Review URL: https://codereview.chromium.org/214513008 git-svn-id: svn://svn.chromium.org/blink/trunk@170221 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
schenney@chromium.org authored
Code to update the blending status in the RenderLayer hierarchy when a child is added or removed current invokes paintsWithBlendMode which calls compositingState() when it should not. This patch removes the compositing state check in this case, which means we may do more work. All existing tests pass. R=senorblanco@chromium.org BUG=343759 Review URL: https://codereview.chromium.org/211103007 git-svn-id: svn://svn.chromium.org/blink/trunk@170220 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
japhet@chromium.org authored
In certain rare cases, history.{push,replace}State are called when during plugin detach. In this case, it's possible for the state modification to be requested on a frame that is half-way detached. The Document is still live, but the DocumentLoader is gone. Exit early in this case. BUG=356424 Review URL: https://codereview.chromium.org/215183002 git-svn-id: svn://svn.chromium.org/blink/trunk@170219 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
enne@chromium.org authored
Revert of Make start/stop loading notifications per-frame (https://codereview.chromium.org/183793002/) Reason for revert: Possibly causing content_browsertests EndToEnd to fail. See: http://build.chromium.org/p/chromium.webkit/builders/Linux%20Tests%20%28dbg%29/builds/2095/steps/content_browsertests/logs/stdio Output: [20917:20917:0327/122353:3268961829:INFO:CONSOLE(0)] "Uncaught TypeError: Cannot convert undefined or null to object", source: http://127.0.0.1:34379/files/web_ui_mojo.html (0) [20917:20917:0327/122353:3269022437:INFO:CONSOLE(28)] "Uncaught TypeError: undefined is not a function", source: http://127.0.0.1:34379/files/web_ui_mojo.js (28) BrowserTestBase signal handler received SIGTERM. Backtrace: #0 0x000000a593be base::debug::StackTrace::StackTrace() #1 0x000002bfc17b content::(anonymous namespace)::DumpStackTraceSignalHandler() #2 0x7f9c3e4ab4a0 <unknown> #3 0x7f9c3e55da43 __poll #4 0x7f9c42aabff6 <unknown> #5 0x7f9c42aac124 g_main_context_iteration #6 0x000000aaaf5f base::MessagePumpGlib::RunWithDispatcher() #7 0x000000a8e802 base::RunLoop::Run() #8 0x00000058256e content::(anonymous namespace)::WebUIMojoTest_EndToEnd_Test::RunTestOnMainThread() Original issue's description: > Make start/stop loading notifications per-frame > > Also, make ProgressTracker a frame-level concept rather than a page-level concept and merge it with FrameLoader's FrameProgressTracker helper. Send per-frame progress change notifications accordingly. > > This depends on https://codereview.chromium.org/180113003/ landing in chromium. > > BUG=347643 > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=170192 TBR=abarth@chromium.org,japhet@chromium.org NOTREECHECKS=true NOTRY=true BUG=347643 Review URL: https://codereview.chromium.org/215533004 git-svn-id: svn://svn.chromium.org/blink/trunk@170218 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
japhet@chromium.org authored
It's possible that MemoryCache::replace will try to evict a resource that has already been evicted. If there is another resource present in its place, it won't get evicted, but will get partially overwritten. In that partial overwrite, we leave references to it in the LRU lists, leading to later crashes. BUG=357174 TEST=MemoryCacheTest.RemoveDuringRevalidation Review URL: https://codereview.chromium.org/214773004 git-svn-id: svn://svn.chromium.org/blink/trunk@170217 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tkent@chromium.org authored
Use didNotifySubtreeInsertionsToDocument instead. BUG=356095 TEST=automated R=morrita@chromium.org Review URL: https://codereview.chromium.org/212793007 git-svn-id: svn://svn.chromium.org/blink/trunk@170216 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
enne@chromium.org authored
BUG=345027 Review URL: https://codereview.chromium.org/207153002 git-svn-id: svn://svn.chromium.org/blink/trunk@170214 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
bajones@chromium.org authored
BUG=352282 Review URL: https://codereview.chromium.org/214963003 git-svn-id: svn://svn.chromium.org/blink/trunk@170213 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rune@opera.com authored
Traverse the selectorList() like we do for :host to find features for invalidation sets. Relevance for 351613 is that we need to support this in order to implement efficient invalidation sets for :hover with childrenAffectedByHover due to UA stylesheet rules. R=esprehn BUG=356125,351613 Review URL: https://codereview.chromium.org/210973004 git-svn-id: svn://svn.chromium.org/blink/trunk@170212 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ch.dumez@samsung.com authored
Add Traversal<*Element>::firstAncestor() API to traverse elements of a specific type. It is a common pattern in our code base to traverse the ancestors of a Node until we find an Element of a specific type. This new firstAncestor() API makes the code much simpler. This CL already makes use of the new API in several places. R=esprehn, eseidel BUG=346733 Review URL: https://codereview.chromium.org/201293002 git-svn-id: svn://svn.chromium.org/blink/trunk@170211 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dglazkov@chromium.org authored
This is a revert of https://src.chromium.org/viewvc/blink?view=rev&revision=168627. BUG=254020 Review URL: https://codereview.chromium.org/215173003 git-svn-id: svn://svn.chromium.org/blink/trunk@170210 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
wolenetz@chromium.org authored
Chromium-side changes to parse and use optional WebM TrackEntry DefaultDuration, derive simpleblock frame durations from subsequent frame duration, or estimate missing frame duration as the maximum duration seen so far cause changes in mediasource buffered range tests. This change updates the tests relative to the new WebM frame duration parsing/derivation/defaulting. Also includes TestExpectations update to allow these tests to fail until Chromium side lands. BUG=351166 TBR=acolwell@chromium.org TEST=All media layout tests pass locally on Linux (with the Chromium prereq CLs applied), and failure is allowed by TestExpectations (without the prereq CLs applied) Review URL: https://codereview.chromium.org/212593007 git-svn-id: svn://svn.chromium.org/blink/trunk@170209 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
enne@chromium.org authored
This is a commit to make https://codereview.chromium.org/205263004/ apply cleanly. TBR=jamesr@chromium.org BUG=345027 Review URL: https://codereview.chromium.org/215353003 git-svn-id: svn://svn.chromium.org/blink/trunk@170208 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
xhwang@chromium.org authored
BUG=356839 Review URL: https://codereview.chromium.org/214983002 git-svn-id: svn://svn.chromium.org/blink/trunk@170207 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
lushnikov@chromium.org authored
This patch changes SetPropertyTextAction to use setStyleText method instead of setPropertyText for the undo operation. This makes it possible to successfully undo multiple property insertions. BUG=341506 Review URL: https://codereview.chromium.org/211193006 git-svn-id: svn://svn.chromium.org/blink/trunk@170206 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
enne@chromium.org authored
This is a follow-up to r170203 to remove even more carriage returns. TBR=jamesr@chromium.org BUG=345027 Review URL: https://codereview.chromium.org/215403002 git-svn-id: svn://svn.chromium.org/blink/trunk@170205 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
enne@chromium.org authored
This is a pre-commit for https://codereview.chromium.org/205263004/ to change the line-endings this file in that patch so that the patch can be applied cleanly in rietveld. TBR=jamesr@chromium.org BUG=345027 Review URL: https://codereview.chromium.org/215383002 git-svn-id: svn://svn.chromium.org/blink/trunk@170203 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
keishi@chromium.org authored
The previous behavior was to select all on mouse down and clear on mouse up. This matched the Cocoa NSSearchField behavior. On Android the button may be so small users couldn't tap it reliably and only mousedown would fire. BUG=329326 Review URL: https://codereview.chromium.org/93863007 git-svn-id: svn://svn.chromium.org/blink/trunk@170202 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
eroman@chromium.org authored
wrap-unwrap.html becomes these files: * wrapKey-unextractable.html * wrapKey-lacks-usage.html * wrapKey-badParameters.html * unwrapKey-lacks-usage.html * unwrapKey-badParameters.html BUG=245025 Review URL: https://codereview.chromium.org/214263002 git-svn-id: svn://svn.chromium.org/blink/trunk@170201 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
timvolodine@chromium.org authored
When firing null-events stop DeviceSensorEventController only after the event has propagated to window. When no sensors are available chrome should fire an all-null event into blink. However at the time of firing the active DOM objects can be suspended or stopped, which can prohibit propagation of the event to window. Currently the controller will be unregistered in any case because the event is a null-event. This results in the potential loss of null-events and the javascript callback is never executed. To avoid this issue the firing of a null-event should happen until it effectively propagates to window. BUG=356750 TEST=http://jsbin.com/pivimoga/1/ (manual) TEST=https://codereview.chromium.org/214763002/ (browsertest) Review URL: https://codereview.chromium.org/212983007 git-svn-id: svn://svn.chromium.org/blink/trunk@170200 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sigbjornf@opera.com authored
R=wibling@chromium.org,haraken@chromium.org BUG=340522 Review URL: https://codereview.chromium.org/214563004 git-svn-id: svn://svn.chromium.org/blink/trunk@170199 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sigbjornf@opera.com authored
Gauge if removing these compatibility properties is feasible. R=jochen@chromium.org BUG=357112 Review URL: https://codereview.chromium.org/214563002 git-svn-id: svn://svn.chromium.org/blink/trunk@170198 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rtoy@chromium.org authored
This is a follow up that adds a simple layout test to test https://codereview.chromium.org/201673004/ This test creates an audio context at 48 kHz and a 3 kHz sine wave in an AudioBuffer that is played through the context. The test verifies that the output is sufficiently close to the expected sine wave output. BUG=344375 Review URL: https://codereview.chromium.org/213153003 git-svn-id: svn://svn.chromium.org/blink/trunk@170197 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
vogelheim@chromium.org authored
This is split out from 206533004, as it's largely unrelated to the remaining changes there. BUG= Review URL: https://codereview.chromium.org/212793013 git-svn-id: svn://svn.chromium.org/blink/trunk@170196 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
a.cavalcanti@samsung.com authored
allows to have less function paramenters. This patch also streamlines a bit the code in calculateUnscaledKernelSize. BUG=356329 Review URL: https://codereview.chromium.org/211513003 git-svn-id: svn://svn.chromium.org/blink/trunk@170195 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
robhogan@gmail.com authored
Revert of Avoid unnecessary descents into nested boxes with floats. (https://codereview.chromium.org/195363007/) Reason for revert: Caused a lot of float crashes in ClusterFuzz https://code.google.com/p/chromium/issues/detail?id=357242 Original issue's description: > Avoid unnecessary descents into nested boxes with floats. > > Steal a bit from RenderBlock to avoid descending through the same > stack of nested boxes multiple times while preparing to lay them out. > > > This CL creates a 4% improvement in the > Performance/Layout/floats_*_nested.html tests. > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=170060 TBR=ojan@chromium.org,leviw@chromium.org,bjonesbe@adobe.com,jchaffraix@chromium.org NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/214523007 git-svn-id: svn://svn.chromium.org/blink/trunk@170194 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pkasting@chromium.org authored
beyond the end of the color table. Instead, draw these pixels as black. This matches Firefox and IE. BUG=176678 TEST=none R=abarth@chromium.org, hclam@chromium.org Review URL: https://codereview.chromium.org/213613002 git-svn-id: svn://svn.chromium.org/blink/trunk@170193 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
japhet@chromium.org authored
Also, make ProgressTracker a frame-level concept rather than a page-level concept and merge it with FrameLoader's FrameProgressTracker helper. Send per-frame progress change notifications accordingly. This depends on https://codereview.chromium.org/180113003/ landing in chromium. BUG=347643 Review URL: https://codereview.chromium.org/183793002 git-svn-id: svn://svn.chromium.org/blink/trunk@170192 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pfeldman@chromium.org authored
TBR=vsevik Review URL: https://codereview.chromium.org/214693006 git-svn-id: svn://svn.chromium.org/blink/trunk@170191 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
Drive-by: Do not subscribe each message to the timestamp display setting but rather the ConsoleMessageView R=eustas, vsevik BUG=357175 NOTRY=true Review URL: https://codereview.chromium.org/214693005 git-svn-id: svn://svn.chromium.org/blink/trunk@170190 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
fmalita@chromium.org authored
This CL removes explicit SkCanvas::SaveFlags from Blink: they are being deprecated in Skia, and we are only passing defaults anyway. R=schenney@chromium.org, reed@google.com, senorblanco@chromium.org Review URL: https://codereview.chromium.org/212643013 git-svn-id: svn://svn.chromium.org/blink/trunk@170189 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
alph@chromium.org authored
Review URL: https://codereview.chromium.org/214713004 git-svn-id: svn://svn.chromium.org/blink/trunk@170188 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
arv@chromium.org authored
BUG=279426 TBR=joaoe@opera.com Review URL: https://codereview.chromium.org/214833003 git-svn-id: svn://svn.chromium.org/blink/trunk@170187 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pfeldman@chromium.org authored
R=caseq@chromium.org Review URL: https://codereview.chromium.org/213003002 git-svn-id: svn://svn.chromium.org/blink/trunk@170186 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
wibling@chromium.org authored
R=ager@chromium.org, erik.corry@gmail.com, haraken@chromium.org, oilpan-reviews@chromium.org, tkent@chromium.org, vegorov@chromium.org, zerny@chromium.org BUG=341815 Review URL: https://codereview.chromium.org/213173002 git-svn-id: svn://svn.chromium.org/blink/trunk@170185 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
marja@chromium.org authored
With this API, we can get rid of the precompilation phase. When the script is compiled the first time, the compilation will produce the lazy function data (the same data which the precompilation used to produce). This data is then cached and used when the script is compiled again. Note that the caching only happens inside one renderer, and the data is not stored on disk. Getting rid of the separate precompilation phase enables various improvements on the V8 side, for example, using multiple threads for parsing: one will run a fast parser to produce the lazy function data, another will run the real (slower) parser and use the lazy function data to skip over functions. Perf note: This doesn't regress morejs warm times. That means that the data is generated and used correctly. BUG= R=haraken@chromium.org Review URL: https://codereview.chromium.org/212983011 git-svn-id: svn://svn.chromium.org/blink/trunk@170183 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
apavlov@chromium.org authored
BUG=357003 TBR=tkent Review URL: https://codereview.chromium.org/214683004 git-svn-id: svn://svn.chromium.org/blink/trunk@170182 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pfeldman@chromium.org authored
TBR=vsevik Review URL: https://codereview.chromium.org/210243005 git-svn-id: svn://svn.chromium.org/blink/trunk@170181 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tkent@chromium.org authored
Oilpan: Move database closing task in ~DatabaseBackendSync to a pre-finalization hook with HeapHashMap. This is a preparation to move DatabaseContext class to Oilpan heap. We need to access a DatabaseContext during closing a database. So, we can't close the database in ~DatabaseBackendSync if we make DatabaseContext class GarbageCollected. We have a HashSet in DatabaseContext to close opening DatabaseBackendSync on context shutdown. - If a DatabaseBackendSync is alive until context shutdown, DatabaseContext can close it as ever. - If a DatabaseBackendSync is garbage-collected before context shutdown, we need to detect it is about to finalized and need to close it. We change the HashSet to HeapHashMap<WeakMember<DatabaseBackendBase>, OwnPtr<DatabaseCloser>>. It realizes pre-finalization hook. BUG=347902 Review URL: https://codereview.chromium.org/214163004 git-svn-id: svn://svn.chromium.org/blink/trunk@170180 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-