- 16 Jun, 2014 6 commits
-
-
jamesr@chromium.org authored
This puts the blink heap asm targets in the GN build set and enables both blink platform test targets behind a single flag. They compile, link and run successfully on mac but (probably) don't link yet on linux due to ffmpeg deps. R=brettw@chromium.org Review URL: https://codereview.chromium.org/332123002 git-svn-id: svn://svn.chromium.org/blink/trunk@176174 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dcheng@chromium.org authored
Page::willBeDestroyed() detachs any frames remaining in the frame tree, so there's no need to do this before calling willBeDestroyed(). In addition, since frameDetached() recursively detaches all frames, eliminate the loop inside Page::willBeDestroyed() to detach all frames. Review URL: https://codereview.chromium.org/339493002 git-svn-id: svn://svn.chromium.org/blink/trunk@176173 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yosin@chromium.org authored
Don't move uneditable paragraph contents in CompositeEditCommand::moveParagraphContentsToNewBlockIfNecessary This patch makes CompositeEditCommand::moveParagraphContentsToNewBlockIfNecessary not to move uneditable paragraph contents. In attached test case, Blink tried to move contents in uneditable ABBR element. BUG=381076, 383811 TEST=LayoutTests/editing/execCommand/justy-center-with-uneditable-crash.html Review URL: https://codereview.chromium.org/335773002 git-svn-id: svn://svn.chromium.org/blink/trunk@176172 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yosin@chromium.org authored
This patch introduces Blink specific CSS classes for editing for - Apple-interchange-newline - Apple-converted-space - Apple-paste-as-quotation - Apple-style-span - Apple-tab-span These CSS classes are defined in "core/editing/HTMLInterchange.h" We would like to deprecate these Blink specific CSS classes for browser compatibility, if possible. BUG=383677 TEST=n/a Review URL: https://codereview.chromium.org/327323005 git-svn-id: svn://svn.chromium.org/blink/trunk@176171 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tkent@chromium.org authored
Revert of Textarea resize-able only to larger; min-height and min-width properly set (https://codereview.chromium.org/239983004/) Reason for revert: Regression for RTL textareas. Original issue's description: > Textarea resize-able only to larger; min-height and min-width properly set > > Textarea does not respect the min-height and min-width property when they are > set by user. When textarea min-height and min-width is set by the user and > if we resize textarea it will only resize to value larger than the width and > heght of textarea and not with value smaller than it's width and height. It > assumes width and height as min-width and min height and does not take into > account the actual min-width and min-height set by user. This patch removes > this bug by initializing the setMinimumSizeForResizing value with min-width > and min-height. > > BUG=94583 > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=173269 BUG=94583,371743 TBR=harpreet.sk@samsung.com, chaffraix@chromium.org Review URL: https://codereview.chromium.org/336143002 git-svn-id: svn://svn.chromium.org/blink/trunk@176170 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mlamouri@chromium.org authored
This will make it possible to get the text surrounding the current selection by calling WebFrame::selectionRange() and passing that range to WebSurroundingText. BUG=330238 Review URL: https://codereview.chromium.org/294073005 git-svn-id: svn://svn.chromium.org/blink/trunk@176168 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 15 Jun, 2014 7 commits
-
-
ch.dumez@samsung.com authored
Remove useless override of executionContext() in HTMLMediaElement. This was previously done to remove ambiguity because HTMLMediaElement inherited two implementations of executionContext() from its base classes (Node and ActiveDOMObject). This CL gets rid of the override and uses a "using" statement instead to remove ambiguity, which is the proper way to do this. The executionContext() override in Node can now be marked as FINAL as a result. R=tkent@chromium.org Review URL: https://codereview.chromium.org/334063002 git-svn-id: svn://svn.chromium.org/blink/trunk@176167 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
erik.corry@gmail.com authored
R=ager@chromium.org, sigbjornf@opera.com BUG=384246 Review URL: https://codereview.chromium.org/338533002 git-svn-id: svn://svn.chromium.org/blink/trunk@176166 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tonyg@chromium.org authored
BUG=384857 TBR=tonyg@chromium.org NOTRY=True NOTREECHECKS=True Review URL: https://codereview.chromium.org/336093002 git-svn-id: svn://svn.chromium.org/blink/trunk@176165 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mlamouri@chromium.org authored
This is removing ~250 files that are not required because they are passing testharness output in an expected file. Adding such file will be prevented via a PRESUBMIT check, see https://codereview.chromium.org/332583002/ BUG=None Review URL: https://codereview.chromium.org/328243002 git-svn-id: svn://svn.chromium.org/blink/trunk@176164 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pdr@chromium.org authored
CachedUAStyles are large (160b) and not cheap to create because they include several Length objects which have non-trivial destructors, making CachedUAStyles expensive to destruct. This patch reduces the number of CachedUAStyles by only creating them when needed. There are two changes in this patch: 1) CachedUAStyle& is no longer a member on StyleAdjuster but is instead passed in through StyleAdjuster::adjustRenderStyle. 2) The cached UA style is now constructed as-needed in StyleResolverState::cacheUserAgentBorderAndBackground. StyleResolverState always owned the CachedUAStyle but this patch makes it explicit by changing the type to OwnPtr<CachedUAStyle>. A null check was needed in RenderTheme::adjustStyle but otherwise CachedUAStyle was not accessed without being set. Before patch: facebook.com - 19,850 CachedUAStyles constructed wikipedia cat - 22,686 CachedUAStyles constructed With patch: facebook.com - 538 CachedUAStyles constructed wikipedia cat - 16 CachedUAStyles constructed Review URL: https://codereview.chromium.org/338673002 git-svn-id: svn://svn.chromium.org/blink/trunk@176163 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dcheng@chromium.org authored
With OOPI, the main frame can be either local or remote. Features that depend on the main frame being local will have to be updated to account for this fact. This patch takes an aggressive approach--most locations that depend on main frame being local have been updated to directly attempt to downcast to LocalFrame, with no attempt to check that the main frame is local first. The only places that check are those on the critical path towards getting rendering/input events working with the updated OOPI infrastructure. BUG=346764 Review URL: https://codereview.chromium.org/336553003 git-svn-id: svn://svn.chromium.org/blink/trunk@176162 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
Also fixes a real bug where we reversed the order of the type/release/debug columns for the list of failing builders, but we didn't adjust cellByBuildType or the tests to account for it. Instead, re-reverse the order. Tests pass, bug fixed. I'm not sure when this bug got introduced, but its at least from before the Blink fork, as are most of these other test failures. NOTRY=true Review URL: https://codereview.chromium.org/332073002 git-svn-id: svn://svn.chromium.org/blink/trunk@176161 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 14 Jun, 2014 18 commits
-
-
dcheng@chromium.org authored
Traditionally, frame tree mutation has been driven from inside the renderer itself. However, for out-of-process iframes, the embedder needs to mirror the same frame tree structure between several different renderers. BUG=346764 Review URL: https://codereview.chromium.org/334483002 git-svn-id: svn://svn.chromium.org/blink/trunk@176159 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
c.shu@samsung.com authored
This CL takes care the fetch, fileapi, frame and part of html subdirs under core. BUG=381876 Review URL: https://codereview.chromium.org/336893002 git-svn-id: svn://svn.chromium.org/blink/trunk@176158 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dominicc@chromium.org authored
BUG=379012 Review URL: https://codereview.chromium.org/324893002 git-svn-id: svn://svn.chromium.org/blink/trunk@176157 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
The biggest change is removing RelativeTime. We were creating these, but not doing anything with them. These were also the only things that ever called setIndex on Notification, so we can remove index/setIndex from Notification. The rest of the patch is just removing dead code. NOTRY=true Review URL: https://codereview.chromium.org/336033002 git-svn-id: svn://svn.chromium.org/blink/trunk@176156 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
robhogan@gmail.com authored
Remove the very complicated logic from computeLogicalHeight() and computeLogicalWidth() whose sole purpose was to use the writing mode of the child vs the containing block when appropriate. The complexity was unnecessary and the same result can be achieved by ensuring we use the child's writing mode when computing the size of the box and the parent's writing mode when computing the margins for position (e.g. for margin collapsing). Review URL: https://codereview.chromium.org/298563002 git-svn-id: svn://svn.chromium.org/blink/trunk@176154 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jamesr@chromium.org authored
Depends on the yasm stuff landing and sticking. Review URL: https://codereview.chromium.org/336633003 git-svn-id: svn://svn.chromium.org/blink/trunk@176153 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
lazyboy@chromium.org authored
We focus the plugin on mousedown/touchstart, so similarly we should focus it on gesturetapdown. This fixes IME input on plugins, if a plugin gets gesturetapdown without any mousedown/touchstart, the plugin will be focused correctly and input fed to the plugin would work properly. This could happen if the plugin doesn't have any touch handlers, then tapping sends gesture event(s) to plugin, without any touchstart. BUG=383484 Test=Using chrome app webview, which is a plugin. Enable virutal keyboard in chrome://flags if it's not enabled. In chromebook pixel: load the sample browser app https://github.com/GoogleChrome/chrome-app-samples/tree/master/webview-samples/browser Navigate to a simple page that has <input> element, e.g. http://jsbin.com/togif/1/ Now without generating any mouse/touchpad inside the content area, tap on the screen on the input box in the jsbin page. Notice virtual keyboard opening and it is possible to type stuffs into the input box. Review URL: https://codereview.chromium.org/333813002 git-svn-id: svn://svn.chromium.org/blink/trunk@176152 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
habib.virji@samsung.com authored
Depending on the inlineBox bidiLevel use the right or left offset. Do not use bidiLevel of the previous box when attribute is auto. R=eseidel, leviw BUG=296847 TEST=TextArea with strong RTL word, when on next line LTR word is entered, caret position is changed. Review URL: https://codereview.chromium.org/302433015 git-svn-id: svn://svn.chromium.org/blink/trunk@176151 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
chrishtr@chromium.org authored
In the process, inline RenderLayerRepainter::setBackingNeedsRepaint's one call site and remove the method. BUG=384520 Review URL: https://codereview.chromium.org/337793004 git-svn-id: svn://svn.chromium.org/blink/trunk@176150 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jsbell@chromium.org authored
Request.method should be ByteString (now supported) Response.status should be assignable Response.statusText should be assignable Response.statusText should be ByteString (now supported) And added tests for assignable properties/invalid ByteStrings. R=falken@chromium.org,horo@chromium.org Review URL: https://codereview.chromium.org/337793003 git-svn-id: svn://svn.chromium.org/blink/trunk@176148 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
The json mirror is apparently better able to scale to load and is less dependent on the buildbot master being in good state. As part of this, we how have a way of querying the step information for the last build on a builder, so we can skip the request and code related to finding out the build number of the latest run. Change the masters data structure to store a url name instead of the whole URL. The url name is the master name to use for constructing URLs. This way buildershandler can use the mirror, but builders.js can continue pointing to the actual master for it's non-json queries. Also, get rid of the force_update code path in buildershandler. This seemed like a good idea at the time, but in practice it just masks errors by making it seem like things are working. The downside of deleting this is that persistent errors loading the JSON won't be noticed until the memcache is flushed for some reason. We should add monitoring of 500s to catch these things earlier. Review URL: https://codereview.chromium.org/337433003 git-svn-id: svn://svn.chromium.org/blink/trunk@176147 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
readline blocks, so reading stdout, then stderr doesn't make any sense because we'll block on each on. So if we print only to one of them, we'll just wait until the process completes. Also, simplify the readline loop in RebaselineOMatic to just use readline instead of poll. That way it avoids missing any output between the last poll and when the process finishes. Review URL: https://codereview.chromium.org/329873005 git-svn-id: svn://svn.chromium.org/blink/trunk@176146 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
eroman@chromium.org authored
BUG=384565,245025 Review URL: https://codereview.chromium.org/333063004 git-svn-id: svn://svn.chromium.org/blink/trunk@176145 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
philipj@opera.com authored
Revert of Disable the HTMLVideoElement-specific prefixed fullscreen API (2nd attempt) (https://codereview.chromium.org/251873002/) Reason for revert: Wait with removal until the unprefixed Fullscreen API has been shipped. Original issue's description: > Disable the HTMLVideoElement-specific prefixed fullscreen API (2nd attempt) > > BUG=346236 > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=172693 Review URL: https://codereview.chromium.org/328303003 git-svn-id: svn://svn.chromium.org/blink/trunk@176144 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
trchen@chromium.org authored
This CL implements frame scrollbar update for the overflow recalc fast path without invoking layout. This fast path first determines whether scrollbars need to be created or removed (in that case, a layout will be needed), and update scrollbars without layout if possible. TEST=fast/transforms/transform-update-frame-overflow.html BUG=354167 Review URL: https://codereview.chromium.org/328023002 git-svn-id: svn://svn.chromium.org/blink/trunk@176143 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
michaelbai@chromium.org authored
Add APIs - WebFrame::brandColor() to get the brand color. - WebFrameClinet::didChangeBrandColor to notify the brand color change. BUG=383941 Intent to implement and ship link https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/nzRY-h_-_ig Review URL: https://codereview.chromium.org/329943004 git-svn-id: svn://svn.chromium.org/blink/trunk@176142 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
http://src.chromium.org/viewvc/blink?view=revision&revision=176121 BUG=383495 TBR=senorblanco@chromium.org Review URL: https://codereview.chromium.org/333973002 git-svn-id: svn://svn.chromium.org/blink/trunk@176139 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
chrishtr@chromium.org authored
squashing layer state. This is no longer necessary after crrev.com/311813005. BUG= Review URL: https://codereview.chromium.org/331563005 git-svn-id: svn://svn.chromium.org/blink/trunk@176138 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
- 13 Jun, 2014 9 commits
-
-
pdr@chromium.org authored
This is a speculative fix for the flakiness we are seeing on the textPath-change-reference2.svg test[1]. The failure is not reproducable locally but appears as if runTest() is never called. This patch refactors the test to not depend on runTest(). In addition, the test ids have been refactored to be understandable. [1] http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20Blink&showAllRuns=true&showExpectations=true&tests=svg%2Fcustom%2FtextPath-change-reference2.svg BUG=384566 TBR=dpranke Review URL: https://codereview.chromium.org/333063003 git-svn-id: svn://svn.chromium.org/blink/trunk@176137 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
Cleaned up style of translatez-removed.html while updating it. Review URL: https://codereview.chromium.org/324363003 git-svn-id: svn://svn.chromium.org/blink/trunk@176136 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
We'd miss any output between the last poll and the end of the process. Also, print out the log lines so that you can see them when looking at the local log. BUG=382248 Review URL: https://codereview.chromium.org/327633003 git-svn-id: svn://svn.chromium.org/blink/trunk@176135 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jschuh@chromium.org authored
SystemParametersInfo will fail if we've disconnected win32k via the sandbox on Win8+. So, just default to nicer font settings for now, since we know the OS supports them. BUG=365160 Review URL: https://codereview.chromium.org/331843004 git-svn-id: svn://svn.chromium.org/blink/trunk@176134 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
falken@chromium.org authored
Intent-to-ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/Ae18uqxjzp8/C4K_J1xpnGwJ BUG=140205 Review URL: https://codereview.chromium.org/330873002 git-svn-id: svn://svn.chromium.org/blink/trunk@176133 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dpranke@chromium.org authored
- mark crypto/rsassa-pkcs1-v1_5-generate-key.html as flaky timeout - mark svg/custom/textPath-change-reference2.svg as flaky failure - mark inspector/console/console-viewport-selection.html as flaky (Fix FlakyTest entry) - virtual/gpu/fast/canvas/canvas-draw-canvas-on-canvas-shadow.html is no longer failing TBR=schenney@chromium.org Review URL: https://codereview.chromium.org/331843006 git-svn-id: svn://svn.chromium.org/blink/trunk@176132 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dpranke@chromium.org authored
The test now appears to time out periodically (i.e., it's not flaky). Reverting. Original description: > Crash test case: > 1. Open page with javascript > 2. Add breakpoint > 3. Stop on breakpoint > 4. Use live edit and save script > The test worked for Chromium revision until May 30. TBR=kostyatinskiy@google.com BUG=none Review URL: https://codereview.chromium.org/331853007 git-svn-id: svn://svn.chromium.org/blink/trunk@176131 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
kenrb@chromium.org authored
Changes to the compositing path meant the toggle of an iframe to having a self-painting layer wasn't getting updated. R=jamesr@chromium.org Review URL: https://codereview.chromium.org/330283008 git-svn-id: svn://svn.chromium.org/blink/trunk@176130 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
feng@chromium.org authored
Break Android build, clearly it was a typo. BUG=357163 Review URL: https://codereview.chromium.org/333943002 git-svn-id: svn://svn.chromium.org/blink/trunk@176129 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-