GitLab

BUG=none
TEST=no layout test failure

Review URL: https://codereview.chromium.org/645743003

git-svn-id: svn://svn.chromium.org/blink/trunk@183644 bbb929c8-8fbe-4397-9dbb-9b2b20218538

This patch adds a set of trace events to track reason when
StyleInvalidator invokes Node::setNeedsStyleRecalc. One of the trace events is guaranteed to be issued before StyleInvalidator issues setNeedsStyleRecalc on the node. The trace events come with InspectorStyleInvalidatorInvalidateEvent, which contains inspector node id, human readable reason string, and optionally the tagName/id/class/attr/invalidationList involved.

This is to be used from devtools so we post process and find the StyleInvalidator trace event on the given node to see the detailed reason for why StyleInvalidator decided issue setNeedsStyleRecalc on the node.

BUG=410701

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=183177

Review URL: https://codereview.chromium.org/580373002

git-svn-id: svn://svn.chromium.org/blink/trunk@183643 bbb929c8-8fbe-4397-9dbb-9b2b20218538

The WebSocket implementation has moved to chrome. As it is stable now, let's
delete the old implementation.
This CL doesn't delete some platform/ and web/ classes, as some chromium-side
code depends on them.

BUG=423201
R=ricea@chromium.org

Review URL: https://codereview.chromium.org/639333003

git-svn-id: svn://svn.chromium.org/blink/trunk@183642 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Remove Overlay Scrollbar if not scrollable along that axis. If the 
scrollSize along that axis is zero then set scrollbar along that
axis to false. This is applicable to Solid-Color scrollbars in Android
& Overlay scrollbars in the Aura.

BUG=415031

Review URL: https://codereview.chromium.org/643933002

git-svn-id: svn://svn.chromium.org/blink/trunk@183641 bbb929c8-8fbe-4397-9dbb-9b2b20218538

BUG=388375,401381
TBR=nhiroki@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/642933008

git-svn-id: svn://svn.chromium.org/blink/trunk@183640 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Together with the Chromium-side patch, makes top controls work properly
under the virtual viewport mode of pinch zoom. The key changes on the
Blink side are to adjust both the PinchViewport and FrameView max scroll
bounds to account for the change in the top controls offset on the
compositor. Additionally, I changed these to make the same floating point
and snapping calculations as in the compositor to prevent losing pixel
fractions.

Chromium side: https://codereview.chromium.org/641873003/

BUG=364109

Review URL: https://codereview.chromium.org/643473002

git-svn-id: svn://svn.chromium.org/blink/trunk@183639 bbb929c8-8fbe-4397-9dbb-9b2b20218538

According to latest editor's draft http://rawgit.com/w3c/html-api-map/master/index.html
meter tag should have MSAA+IA2 Role as ROLE_SYSTEM_PROGRESSBAR and
AX role as AXGroup and Role description as "group"

BUG=421376

Review URL: https://codereview.chromium.org/652663003

git-svn-id: svn://svn.chromium.org/blink/trunk@183638 bbb929c8-8fbe-4397-9dbb-9b2b20218538

This CL adds a fast, conservative way to determine if we are in the main thread.

1) In ThreadState::init(), take the underestimated size of the main thread.

2) When ThreadState::current() is called, check if the current stack address is within the underestimated size from the stack start of the main thread. If yes, we can immediately return the mainThreadState() without looking up TLS. Otherwise, we look up TLS.

TLS is very slow especially in Mac and Windows. This CL improves blink_perf.parser.querySelector-* (and other) benchmarks by 6% in Mac.

BUG=420515

Review URL: https://codereview.chromium.org/643883002

git-svn-id: svn://svn.chromium.org/blink/trunk@183637 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Currently we count CSS properties in CSSPropertyParser::parseValue (the
non-static version). This function is used recursively for shorthands,
so we end up tracking many CSS properties which haven't been specified
by users.

This patch moves the check up a level, so that it is only called on
properties specified by a user. I've also made it only count properties
that succeeded at parsing (behaviour wouldn't change for declarations
that fail to parse if we removed the property).

This should reduce the usage numbers on chromestatus.com for many
properties. For example while border-spacing is not specced as a
shorthand, it is implemented as a shorthand and we end up measuring
-webkit-border-horizontal-spacing whenever we parse border-spacing.

Review URL: https://codereview.chromium.org/642583006

git-svn-id: svn://svn.chromium.org/blink/trunk@183636 bbb929c8-8fbe-4397-9dbb-9b2b20218538

I misremoved the UseCounter in the process of moving marquee implementation
to JS. This CL readds the UseCounter.

Review URL: https://codereview.chromium.org/653753003

git-svn-id: svn://svn.chromium.org/blink/trunk@183635 bbb929c8-8fbe-4397-9dbb-9b2b20218538

The Slimming Paint codepath wasn't properly adding paint offsets
to the applied clip rects, causing only a fraction of text to be
drawn. Also adding a debug red background to make it more obvious
when we're failing to paint. Cribbed from FrameView's old paint
code.

BUG=423071

Review URL: https://codereview.chromium.org/654713003

git-svn-id: svn://svn.chromium.org/blink/trunk@183634 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Tried to improve readability. Also re-arranged the for-loop a bit.

This CL is part of splitting up [1].

[1] https://codereview.chromium.org/639433002

R=chrishtr@chromium.org

Review URL: https://codereview.chromium.org/652703002

git-svn-id: svn://svn.chromium.org/blink/trunk@183633 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Unify the pixel snapping logic for selection rects by moving the logic
into selectionRectForText and having selectionRectForSimpleText and
selectionRectForComplexText respectively return precise values.

R=fmalita@chromium.org

Review URL: https://codereview.chromium.org/648633003

git-svn-id: svn://svn.chromium.org/blink/trunk@183632 bbb929c8-8fbe-4397-9dbb-9b2b20218538

BUG=410411
TEST=no visible change

Review URL: https://codereview.chromium.org/655613002

git-svn-id: svn://svn.chromium.org/blink/trunk@183631 bbb929c8-8fbe-4397-9dbb-9b2b20218538

BUG=417463

Review URL: https://codereview.chromium.org/648223003

git-svn-id: svn://svn.chromium.org/blink/trunk@183630 bbb929c8-8fbe-4397-9dbb-9b2b20218538

This new event is of type MediaEncryptedEvent, which has initDataType instead of contentType (but this CL just renames one to the other, without translation), and changes the type of initData from Uint8Array to ArrayBuffer as per the WD EME spec.

Also in this CL:
  - Start renaming keyNeeded() to encrypted() by renaming the it on HTMLMediaElementEncryptedMedia.
  - Remove unused contentType argument from createWebkitNeedKeyEvent() (good thing it's unused or the contentType to initDataType change would be a lot harder).
  - Fix prefixed/encrypted-media-events.html test to test the prefixed needkey event instead of the unprefixed one.

TBR=jochen@chromium.org,ddorwin@chromium.org
BUG=224786
(cherry picked from commit ad09c3ed1914691ee4a089cfe95988892ed42407)

Review URL: https://codereview.chromium.org/655603003

git-svn-id: svn://svn.chromium.org/blink/trunk@183628 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Update the API for WebContentDecryptionModule and
WebContentDecryptionModuleSession in order to implement
the latest EME API spec.

BUG=224786
TEST=Adding to API, no code using it. All existing EME tests pass.

Review URL: https://codereview.chromium.org/642583003

git-svn-id: svn://svn.chromium.org/blink/trunk@183627 bbb929c8-8fbe-4397-9dbb-9b2b20218538

This patch switches to "Causes" for explaining timeline records. The
major change is "Stacks" have been renamed "Causes". This is prepwork
for two upcoming projects: invalidation tracking which will fill out many
more causes, and javascript samples which are easily confused with
the "stack" term. If the causes checkbox is not checked, no initiator
or stack information will be shown.

Some minor rewording of the causes has also been done. For example,
the stack for a layout now reads "First layout invalidation" instead of
"Layout invalidated".

A screenshot is available at http://pr.gg/justcause3.png

BUG=410701

Review URL: https://codereview.chromium.org/631573002

git-svn-id: svn://svn.chromium.org/blink/trunk@183626 bbb929c8-8fbe-4397-9dbb-9b2b20218538

The 'parent' argument is not used, remove it.

This implicitly fixes an incorrect invocation of the constructor from
ScrollAnimatorNoneTest::SavePerAxisData, which following r183583 was
passing in an uninitialized pointer value as argument.

R=mkwst
BUG=

Review URL: https://codereview.chromium.org/648273002

git-svn-id: svn://svn.chromium.org/blink/trunk@183625 bbb929c8-8fbe-4397-9dbb-9b2b20218538

https://src.chromium.org/viewvc/blink?view=rev&revision=183172 .

BUG=81439
TEST=none
TBR=jamesr

Review URL: https://codereview.chromium.org/641643004

git-svn-id: svn://svn.chromium.org/blink/trunk@183624 bbb929c8-8fbe-4397-9dbb-9b2b20218538

In pinch viewport mode, the size of the FrameView is always the content
width of the document (not the true viewport size), so this patch plumbs
the viewport size to fullscreen elements separately.  Secondly, in this
mode there is an "inner viewport" that scrolls separately and whose
scrollability additionally needs to be disabled.  Do so by using
setUserScrollable() (which is a mechanism that only works in this mode).

BUG=411072

Review URL: https://codereview.chromium.org/636363003

git-svn-id: svn://svn.chromium.org/blink/trunk@183623 bbb929c8-8fbe-4397-9dbb-9b2b20218538

This is blink side CL to expose input type radio button with menu as parent with
correct IA2 role similar to aria role menuitemradio.

BUG=422879

Review URL: https://codereview.chromium.org/651893002

git-svn-id: svn://svn.chromium.org/blink/trunk@183622 bbb929c8-8fbe-4397-9dbb-9b2b20218538

This CL encapsulates the simple/complex logic in a low level glyphBuffer builder function, and removes all paint-related codepath-specific methods. Everything above buildGlyphBuffer() now operates on a codepath-agnostic data structure (glyphBuffer).

To pull this off, the CL unifies GlyphBuffer & GlyphBufferWithOffsets by adding offset support to the former. The approach has no downside beyond a slightly increased stack frame size for the simple path, and is aligned with plans to eventually store offsets for simple text also (and possibly drop advances altogether).

Also, most text blob caching logic is relocated down into Font drawText() - which allows us to trivially add support for complex text blobs (currently still off due to the lack of offsets support in buildTextBlob). The advance return value (which doesn't play well with blob caching) is dropped, and the only existing client for it is converted to use a new dedicated, blob-cache-bypassing drawUncachedText() method.

R=jbroman@chromium.org,eae@chromium.org,dominik.rottsches@intel.com,leviw@chromium.org

Review URL: https://codereview.chromium.org/645363003

git-svn-id: svn://svn.chromium.org/blink/trunk@183620 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Fetch the actual fill from the various paint-server RenderSVGResources
into a new "data blob" SVGPaintServer. This makes said resources
independent of the GC, and means that GC-state can be managed more
directly by the caller.
Since this makes postApplyResource useless, it's removed, and
applyResource is renamed to preparePaintServer.
Some functions residing on RenderSVGResource is moved to SVGPaintServer.
Paint-server fetch+application is moved to updateGraphicsContext, which
is also changed to return a bool indicating if a paint-server is
available. Handling of clip-path-as-mask is also moved here.

BUG=420022

Review URL: https://codereview.chromium.org/638933002

git-svn-id: svn://svn.chromium.org/blink/trunk@183619 bbb929c8-8fbe-4397-9dbb-9b2b20218538

All uses appear to have been removed from the codebase.

BUG=417463
TBR=adamk@chromium.org

Review URL: https://codereview.chromium.org/650933002

git-svn-id: svn://svn.chromium.org/blink/trunk@183618 bbb929c8-8fbe-4397-9dbb-9b2b20218538

BUG=417275

Review URL: https://codereview.chromium.org/602783002

git-svn-id: svn://svn.chromium.org/blink/trunk@183616 bbb929c8-8fbe-4397-9dbb-9b2b20218538

This step is a giant search and replace for OVERRIDE and FINAL to
replace them with their lowercase versions.

BUG=417463

Review URL: https://codereview.chromium.org/652693002

git-svn-id: svn://svn.chromium.org/blink/trunk@183614 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Currently we use 2 marking threads regardless of the number of processors available.
Given that the marking phase takes a substantial amount of time,
this CL changes the number of marking threads to min(the number of processors, 4).

This CL also decreases the block size of each CallStack from 200 to 128
because load balancing is not good in some benchmarks such as LargeDistributionWithoutLayout. This CL improves LargeDistributionWithoutLayout by 10% for example.

BUG=420515

Review URL: https://codereview.chromium.org/648633002

git-svn-id: svn://svn.chromium.org/blink/trunk@183613 bbb929c8-8fbe-4397-9dbb-9b2b20218538

The problem arises due to the fact that treeElement value is not updated
at the moment of keyDown/keyPress events. The "input" event should be
handled for the proper text value.

BUG=422928
R=apavlov

Review URL: https://codereview.chromium.org/650123002

git-svn-id: svn://svn.chromium.org/blink/trunk@183612 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Revert of Catch uncaught promise rejections from V8 and log to console. (patchset #13 id:520001 of https://codereview.chromium.org/625943002/)

Reason for revert:
This is likely the cause of breakage for these browser_tests:
ManageProfileUITest.Create_NameUpdateOnAvatarSelected
ManageProfileUITest.Create_NoNameUpdateOnAvatarSelectedAfterRevert
ManageProfileUITest.Create_NoNameUpdateOnAvatarSelectedAfterEdit


https://build.chromium.org/p/chromium.mac/builders/Mac10.6%20Tests%20%281%29/builds/56670

Original issue's description:
> Catch uncaught promise rejections from V8 and log to console.
> 
> Print error messages to DevTools console for rejected Promises that are unhandled by the platform end-of-turn.
> 
> BUG=393913
> R=pfeldman, yurys
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=183464
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=183598

TBR=pfeldman@chromium.org,yurys@chromium.org,jl@opera.com,aandrey@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=393913

Review URL: https://codereview.chromium.org/650203003

git-svn-id: svn://svn.chromium.org/blink/trunk@183611 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Revert of Different fonts selected for width calculation and actual painting (patchset #6 id:180001 of https://codereview.chromium.org/593673003/)

Reason for revert:
This broke fast/css/font-face-opentype.html and fast/text/line-break-after-question-mark.html on WinXP

https://sheriff-o-matic.appspot.com/blink/failure/webkit_tests%3A%3Afast%2Fcss%2Ffont-face-opentype.html%3A%3Awebkit_tests%3A%3Afast%2Ftext%2Fline-break-after-question-mark.html

Original issue's description:
> In some cases different fonts are selected to get width of string and
> to draw text.
> In Font.cpp calls, font get changed due to fallback font architecture.
> When making calls we need to check if Unicode is present in primary font or not.
>  In case of Ellipsis, we need to check if Ellipsis Unicode is present in primary font or not,
> if not then use "Dot" Unicode, this is also suggested in CSS3 (http://www.w3.org/TR/2003/CR-css3-text-20030514/)
> 
> BUG=416425
> TEST=fast/text/ellipsis-platform-font-change.html
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=183597

TBR=eae@chromium.org,behdad@chromium.org,tkent@chromium.org,h.joshi@samsung.com
NOTREECHECKS=true
NOTRY=true
BUG=416425

Review URL: https://codereview.chromium.org/648233002

git-svn-id: svn://svn.chromium.org/blink/trunk@183609 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Tracing state management happens on the browser side. So the local state does nothing.
Also if DevTools window was closed when tracing was active the next DevTools session had
this flag enabled. So it was not possible to correctly process tracing data because they
had no TracingStartedInPage event. The state used to be necessary when we had console.timeline/timelineEnd implementation.

This test case has been covered by timeline-trivial.html

BUG=420008
R= yurys@chromium.org, caseq@chromium.org, pfeldman@chromium.org

Review URL: https://codereview.chromium.org/638673002

git-svn-id: svn://svn.chromium.org/blink/trunk@183608 bbb929c8-8fbe-4397-9dbb-9b2b20218538

TBR=eae

Review URL: https://codereview.chromium.org/648223002

git-svn-id: svn://svn.chromium.org/blink/trunk@183607 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Promptly let go of a memory cache entry's Resource when evicting it,
and do not wait until the next GC to strike. This provides the same
behavior & lifetime for the resource as non-Oilpan.

R=mkwst
BUG=420068

Review URL: https://codereview.chromium.org/649213002

git-svn-id: svn://svn.chromium.org/blink/trunk@183606 bbb929c8-8fbe-4397-9dbb-9b2b20218538

http://src.chromium.org/viewvc/blink?view=revision&revision=183597

BUG=416425
TBR=h.joshi@samsung.com

Review URL: https://codereview.chromium.org/654563002

git-svn-id: svn://svn.chromium.org/blink/trunk@183605 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Before this patch console message contains incorrect line number of code in InjectedScriptSource._evaluateOn function.
With this patch this message contains correct script id, line number and column number.

Review URL: https://codereview.chromium.org/566883002

git-svn-id: svn://svn.chromium.org/blink/trunk@183603 bbb929c8-8fbe-4397-9dbb-9b2b20218538

TBR=haraken,oilpan-reviews
BUG=
NOTRY=true

Review URL: https://codereview.chromium.org/648193002

git-svn-id: svn://svn.chromium.org/blink/trunk@183602 bbb929c8-8fbe-4397-9dbb-9b2b20218538

https://crrev.com/6bffde4d87f7a05e5a871cd48366d56b8b83e950 introduces
dispatching of messages on InspectorFrontendAPI post the
IFH.loadCompleted() call only, hence the IFAPI.loadCompleted() call
is no longer required.

R=pfeldman@chromium.org

Review URL: https://codereview.chromium.org/644493003

git-svn-id: svn://svn.chromium.org/blink/trunk@183601 bbb929c8-8fbe-4397-9dbb-9b2b20218538

Using a LengthPoint for this property makes it possible to use
a converter rather than custom code, and it makes animation
building cleaner too.

The setPerspectiveOrigin[X,Y] are kept because of the corresponding
prefixed properties, but they can be removed eventually.

Review URL: https://codereview.chromium.org/643893002

git-svn-id: svn://svn.chromium.org/blink/trunk@183600 bbb929c8-8fbe-4397-9dbb-9b2b20218538

This was broken by the async module loading.

R=pfeldman@chromium.org,dgozman

Review URL: https://codereview.chromium.org/648153002

git-svn-id: svn://svn.chromium.org/blink/trunk@183599 bbb929c8-8fbe-4397-9dbb-9b2b20218538