Annotate a LeakSanitizer false positive in BitVector.

When BitVector allocates memory, it shifts the pointer by 1 before storing it.
LeakSanitizer cannot recognize such pointers, so the memory is reported as
leaked. Annotate the allocation site to silence the leak reports.

BUG=242672
R=thakis@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@163919 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use an enum on ChromiumDataObjectItem for kind.

This removes its dependency on strings declared in DataTransferItem,
and thus reduces the dependency of CDO on core/.

The strings returned to the DOM can be declared statically inside
the scope of DataTransferItem::kind, now that they no longer need
to be exposed to other classes.

BUG=328079

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

git-svn-id: svn://svn.chromium.org/blink/trunk@163920 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove several calls to Page::mainFrame

All of these callers either didn't need to use the mainFrame
(as in the case of the MediaQuery functions which called
PlatformScreen functions which already jumped to the top-most
Widget automatically) or could get the information they need
by asking the Frame directly.

There were a couple cases in the inspector where checking
Frame::isMainFrame() wouldn't be identical, so I've left
those as FIXMEs for now.

R=abarth@chromium.org
BUG=305811

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

git-svn-id: svn://svn.chromium.org/blink/trunk@163921 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove several needless dependencies on Page

Most of these were just needless includes.
There are a few cases of code checking Document::page()
when I think what it really wants is Document::isActive().

I may try to remove Document::page() in a follow-up patch.

BUG=305811
R=abarth@chromium.org

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

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