GitLab

This CL deletes a bunch of state and code from GraphicsLayer that's not used.

R=jamesr@chromium.org

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

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

NOTRY=true
BUG=383741,383742

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

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

BUG=369451

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

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

r175772 changed lifetime of SVGViewSpec to be always same as SVGSVGElement,
so this weak-ref can now be made a strong-ref.

BUG=357163

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

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

The items that are set to flex-wrap and have a single flex line currently
has their cross size adjusted according to the max of the items cross size.
According to the specification section 9.4 number 8 point, it states that:

If the flex container has only one flex line (_even if it’s a multi-line
flex container_) and has a definite cross size the cross size of the flex line
is the flex container’s inner cross size.

link: http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/#cross-sizing

This patch fixes this bug by removing the condtion that checks if it's
a multiline container or not and based on that set flex line cross size.

Bug=362848

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

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

The scrollingCoordinatorEnabled setting is redundant with acceleratedCompositingEnabled.

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

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

SetWrapperReferenceTo IDL attribute is a hack to use V8 wrapper reference
to avoid reference cycles in Blink. The |visitDOMWrapper| callback is
used to create a temporary strong reference between the wrappers in GC
prologue.

Before this patch, |visitDOMWrapper| was allowed to create a new wrapper
if the wrapper for target object didn't exist. However this is dangerous,
as the target object may be already destructed. The target wrapper must
already exist for this reference hack to work correctly.

This patch forbids creating a new wrapper from |visitDOMWrapper| callback,
and adds an ASSERT that checks that the target object wrapper already
exists.

BUG=None

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

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

BUG=381876

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

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

This function just returns whether we're the main frame.

R=jamesr@chromium.org

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

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

ByteString is like DOMString, but should throw TypeError 
during the V8->C++ hop if script tries to set a string with a 
code unit greater than 0x00FF. No enforcement is done on the 
C++->V8 side.

R=nbarth@chromium.org
BUG=347426

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

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

Make all CSSSelector data members private. Previously, some of the data members
such as m_relation / m_match / m_pseudoType were public and accessed directly
from outside the class. The new approach is better because:
- Those members are bit fields so by using getters, we can hide the casts inside
  the getters. The setters can now also check that the bitfield is big enough to
  actually store the enum value.
- When using those in switch() statements, the compiler now complains if we fail
  to test some of the enum values as the value is now an enum, and not merely an
  unsigned integer.
- Some of these members already has getters (e.g. relation(), pseudoType()).
- Better encapsulation.

R=esprehn@chromium.org

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

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

Removes <style scoped>.

This was discussed and approved with LGTMs in blink-dev:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/R1x18ZLS5qQ/Bjuh_cENhlQJ

Chrome status dashboard entry:
http://www.chromestatus.com/features/5374137958662144

The previous one failed to land due to stale generated file issues and browser test failures (3 times):
https://codereview.chromium.org/310443002/ (original CL)
http://crrev.com/175550 -> http://crrev.com/175552 (stale generated file issue)
http://crrev.com/175555 -> http://crrev.com/175561 (stale generated file issue)
http://crrev.com/175720 -> http://crrev.com/175754 (browser test failures)

Browser test failure was due to HTMLStyleElement refcounting mismatch
in ShadowRoot.  This CL fixes the issue and adds a layout test
fast/css/shadow-style-removed-out-of-document.html
to catch the condition.

Note:
This is based on esprehn's original cl:
https://codereview.chromium.org/214693002/

BUG=379096
TEST=pass all layout tests and do not break any existing tests

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

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

Our support for position: sticky isn't even in the experimental feature set. We
shouldn't be burning time during every frame checking whether any RenderLayers
have sticky position.

R=esprehn@chromium.org

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

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

This patch adds WebFont.PackageFormat histogram that tracks the usage of
different format of web fonts. It records container format of font file;
both TrueType fonts and OpenType fonts are recorded as SFNT format.
If a font didn't pass OTS sanitization, it's recoreded as Unknown.

BUG=380988
TEST=manually tested with chrome://histograms

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

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

This removes two Persistent<>s, and add one Persistent<>.

BUG=

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

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

The deleted code was used to ensure the ASSERT(!isAnimating()) on ~SVGAnimatedProperty.
The assert checks that animation is always stopped when the element is dead. However, the assert is removed now, so we don't need to ensure it.

The deleted code |clearAnimatedType| in ~SVGAnimateElement was triggered when a document was unloaded and its <animate> element was destructed before its target svg element. This stopped animation on the target svg elements before the ASSERT run.

BUG=370834

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

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

This provides CacheStorage, the namespace of caches, although without
serialization. The idea is to let us test this API end-to-end early,
and we can replace it with something more sophisticated as we
progress.

R=jsbell@chromium.org,falken@chromium.org,jkarlin@chromium.org,asanka@chromium.org,slightlyoff@chromium.org,jakearchibald@chromium.org
TBR=jochen@chromium.org
BUG=374822

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

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

This CL is a simple s/if !ASSERT_DISABLED/if ASSERT_ENABLED/.
Subsequent CLs will clean up the remaining uses and then delete the macro.

NOTRY=true
R=dglazkov@chromium.org

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

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

fastMod has been dead code for over one year (since I removed the only call site):
https://chromiumcodereview.appspot.com/14718009

isDrawingToLayer is trivial, and its only call site is inside GraphicsContext.

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

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

Fix some SVGFonts compilation errors that are seen when turning off the compile time flag SVG_FONTS.

BUG=

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

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

Since we don't have the SVGInstance tree anymore we can get rid of this
template dispatcher.

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

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

This is based on an earlier patch from <fs@opera.com>.

The performance regression mostly came from excessive tree walks
on SVG_SvgCubics (with only a tiny part of it came also from
extra invalidations).

This change re-introduces what
SVGRenderSupport::checkForSVGRepaintingDuringLayout was doing to
prevent invalidation by checking if your parent had a transform
change, except that we use it to avoid entire subtree walks.

On my Z620, this changes the results of SVG_SvgCubics as follows:
- RAL without patch: 16 ms (std: 0.5)
- RAL with patch: 8.8 ms (std: 0.4)
- Pre-RAL: 9.2 ms (std: 0.3)

BUG=381138

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

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

The Dock button should be the rightmost one, otherwise it gets overlapped
by a button to its right (Settings).

R=eustas, pfeldman@chromium.org, vsevik
BUG=383313

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

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

This CL is a bit of a parlor trick, but it seems worthwhile to remove
DeprecatedDirtyCompositingDuringCompositingUpdate.

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

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

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

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

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

There is no callers for these functions in
Chromium so they can be safely removed.

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

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

This is somewhat hot (about 0.8% of samples while painting glyphs), is
really trivial once inlined (a few moves and a few adds).

SkRect.h is a pretty lightweight header, so this shouldn't affect build
times very much.

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

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

Actually two refactorings for navigator.serviceWorker.ready which is
sensitive to lifetimes. No change in behavior.

First, ServiceWorkerContainer is a DOMWindowLifecycleObserver to
access a window for postMessage. But it already has an execution
context that can provide the DOMWindow. Use that instead.

Second, adds an unrelated assertion that the container's
ServiceWorkerContainerClient has been cleaned up by the time that the
container is deleted. To do otherwise is to leave the
ServiceWorkerContainerClient with a dangling pointer to the container.

BUG=363967

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

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

* MaskImageChanged: No one did anything based on this notification.
* VideoChanged: There's only want caller and it's simpler to just
  setNeedsCompositingUpdate, which does the same thing.
* FullScreenChanged: No one ever sent this notification.

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

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

BUG=340522
TBR=darin

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

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

This CL starts the renaming of RenderObject methods from repaint to
paint invalidation. In this CL I've converted the following:
 repaint
 repaintRectangle
 repaintUsingContainer
 repaintAfterLayoutIfNeeded
 repaintOverflow
 repaintOverflowIfNeed

BUG=338691

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

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

We don't need the templates in ContainerNodeAlgorithms now,
lets start merging them into ContainerNode.

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

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

Replace compile time guard with runtime flag in blink and remove ENABLE_FAST_MOBILE_SCROLLING in gyp file.

The effort needs to be done in 3 steps:
1. Create the runtime flag interface in blink;
2. Enable the flag for Android from chromium even it does not do anything in blink;
3. Replace compile time guard with runtime flag in blink and remove ENABLE_FAST_MOBILE_SCROLLING in gyp file.

This is the 3rd set of changes.

BUG=381391

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

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

Reason for revert:
Suspected cause of crash when running Speedometer on the perf bots: https://code.google.com/p/chromium/issues/detail?id=383338

Original issue's description:
> Enable Oilpan by default in modules/speech/
> 
> R=dmazzoni@chromium.org,haraken@chromium.org,tommi@chromium.org,tkent@chromium.org
> BUG=340522
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175872

TBR=oilpan-reviews@chromium.org,haraken@chromium.org,dmazzoni@chromium.org,tommyw@chromium.org,tommi@chromium.org,tkent@chromium.org,sigbjornf@opera.com
NOTREECHECKS=true
NOTRY=true
BUG=340522

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

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

This will allow debugger to pause on "load", "error" and etc. event breakpoints only
when they happen on XHR event targets.

BUG=381470
R=yurys, pfeldman@chromium.org

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

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

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

BUG=245436,327641

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

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

This change started as a removal of stale entries in the file
(mostly related to font-stretch - that was rolled out - along
with some misc values).

Then I looked at the file and found out that we still referred
to KHTML and CSS_PROP* (none of which make any sense) so I
cleaned up the comments too.

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

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

Change the compositing/gestures tests to avoid a problem where one pixel
is one shade of green lighter due to the underline bleeding through the
rounded corners of the rect. Also change position/size calculation to
use getBoundingClientRect which is faster and more reliable.

BUG=378610
R=dglazkov@chromium.org

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

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

GraphicsContext::scale takes a FloatSize, which is not the way most
callers wish to invoke it. Here we change it to take x and y scale.

GraphicsContext::getCTM is not truly reflective of the tranforms
applied to get a pixel on the screen, as it ignores compositor applied
transforms. There are numerous locations where the CTM is used to test
pixel-level results, such as the width of a line. These tests are not
accurate in the presence of high DPI or other zoom factors. Each
location gets a FIXME indicating the problem.

R=fmalita,esprehn
BUG=383070,382491

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

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

BUG=None
R=loislo@chromium.org

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

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