- 11 Sep, 2014 40 commits
-
-
jdduke@chromium.org authored
WebTouchEvents passed to plugins no longer use the changedTouches or targetTouches properties, rebaseline appropriately. TBR=loislo@chromium.org,jianli@chromium.org BUG=413098 Review URL: https://codereview.chromium.org/563643003 git-svn-id: svn://svn.chromium.org/blink/trunk@181828 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ager@chromium.org authored
TBR=yosin@chromium.org BUG=388681 Review URL: https://codereview.chromium.org/560653003 git-svn-id: svn://svn.chromium.org/blink/trunk@181827 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
morrita@chromium.org authored
This follows the lates spec update: https://www.w3.org/Bugs/Public/show_bug.cgi?id=23170 R=dglazkov@chromium.org BUG=408272 TEST=import-defaultView.html, import-script-prototypes.html Review URL: https://codereview.chromium.org/560183002 git-svn-id: svn://svn.chromium.org/blink/trunk@181826 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
timloh@chromium.org authored
This patch separates the public API of BisonCSSParser from the hundreds of public methods it exposes. The plan is to build a new parser based on the css-syntax specification, which will eventually complete replace the bison-based parser. The functions in this class will do the run-time switching between the bison parser and the new (unwritten) parser. For the functions here which are only ever used with a newly instantiated BisonCSSParser, I've moved instantiation to inside the CSSParser so that the functions can be static. This is an updated version of a patch by eseidel from 8 months ago: https://codereview.chromium.org/112933010/ BUG=330389 Review URL: https://codereview.chromium.org/566483002 git-svn-id: svn://svn.chromium.org/blink/trunk@181825 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
loislo@chromium.org authored
This reverts commit 44cef15dcdbf3b78339c3678fe533f3a97e59870. The patch were reverted due to problem with uninitialized memory. BUG=413229 TBR= jianli@chromium.org, dominik.rottsches@intel.com Review URL: https://codereview.chromium.org/557823003 git-svn-id: svn://svn.chromium.org/blink/trunk@181824 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
grunell@chromium.org authored
This allows MediaStreamTrack::getSources to go through UserMediaClient. To land after this: Chrome CL part 1: https://codereview.chromium.org/562643003/ Blink CL part 2: https://codereview.chromium.org/559423002 Chrome CL part 2 (TBD) BUG=406094 Review URL: https://codereview.chromium.org/560843002 git-svn-id: svn://svn.chromium.org/blink/trunk@181822 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mkwst@chromium.org authored
Rather than passing the wildcard disposition of CSPSource's hosts and ports as booleans, we should have an enum that allows us to figure out hat we mean at the callsite. This patch adds CSPSource::WildcardDisposition in order to make this clear. Review URL: https://codereview.chromium.org/568433002 git-svn-id: svn://svn.chromium.org/blink/trunk@181821 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
yurys@chromium.org authored
DevTools uses TracingStartedInWorker trace event to figure out which worker threads correspond to the inspected page. The events were written on the worker thread which is racy. Current implementation always writes the event on the main thread. Since Tracing.start/end commands are handled on the main thread this eliminates racy behavior. BUG=401895,405429 Review URL: https://codereview.chromium.org/552323002 git-svn-id: svn://svn.chromium.org/blink/trunk@181820 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
dgozman@chromium.org authored
BUG=394734 Review URL: https://codereview.chromium.org/555433002 git-svn-id: svn://svn.chromium.org/blink/trunk@181819 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
alexclarke@chromium.org authored
In Normal mode (the default), there's virtually no prioritization of compositor events, and shouldYieldForHighPriorityWork always returns false. In CompositorPriority mode, there *is* prioritization of compositor tasks and shouldYieldForHighPriorityWork will return false if there are pending high priority events. Currently there is no way for client code to set the policy but that will be introduced in a follow up CL. Also adds some disabled by default tracing in "blink.scheduler" to track the number of pending high priority tasks and which policy mode the scheduler is in. BUG=391005,411520 Review URL: https://codereview.chromium.org/559973003 git-svn-id: svn://svn.chromium.org/blink/trunk@181818 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mkwst@chromium.org authored
This patch begins using the static version of the mixed content checker which was introduced in https://codereview.chromium.org/537983002/. It also takes the opportunity to rework the error message to use the new type information we've now passed into the checker. This patch only touches the ResourceFetcher usage; future patches will clean up the other points in the code where we grab a MixedContentChecker from the loader, and eventually remove the object creation entirely. This will make the site isolation folks happy. BUG=411184 Review URL: https://codereview.chromium.org/561153002 git-svn-id: svn://svn.chromium.org/blink/trunk@181817 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
keonho07.kim@samsung.com authored
Currently, AudioBuffer is supported 3.0KHz to 192.0 KHz. However, offlineAudioContext is not supported lower sample rate than 44.0KHz. http://webaudio.github.io/web-audio-api/#the-audiobuffersourcenode-interface “Describes the sample-rate of the linear PCM audio data in the buffer in sample-frames per second. An implementation must support sample-rates in at least the range 22050 to 96000” Changed supported sampleRate range 3KHz to 192KHz and fftsize for convolution. BUG=394009 Review URL: https://codereview.chromium.org/375383002 git-svn-id: svn://svn.chromium.org/blink/trunk@181816 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mkwst@chromium.org authored
This patch moves CSP generation out of FrameLoader and into DocumentLoader in order to ensure that the 'frame-ancestors' directive can properly block loading a document. The current implementation checks too late in the loading process. The new implementation works, with the caveat that it breaks both console messages and violation reports. Since we have no ExecutionContext, we have nothing to dump console messages into. This work will be covered in https://crbug.com/412725 BUG=411889,411600,357462 Review URL: https://codereview.chromium.org/563473002 git-svn-id: svn://svn.chromium.org/blink/trunk@181814 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
loislo@chromium.org authored
BUG=24182 TBR= jianli@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/562123003 git-svn-id: svn://svn.chromium.org/blink/trunk@181813 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jl@opera.com authored
Like we do for all integer types, use helper functions from V8Binding.h to convert from v8::Value to native types. These helper functions throw all exceptions via their ExceptionState& argument, which means we don't need to initialize a v8::TryCatch in the caller. The helpers initialize a v8::TryCatch if they call in to V8 to convert a value, but they do not do this if the value is already of the correct type. Review URL: https://codereview.chromium.org/567503002 git-svn-id: svn://svn.chromium.org/blink/trunk@181812 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mkwst@chromium.org authored
This patch finishes the process of allowing policy parsing outside of an ExecutionContext, and adjusts Document::initContentSecurityPolicy to accept a ContentSecurityPolicy object rather than a set of headers. If such an object is provided, the document will take ownership of it and use it going forward. If no such object is provided, an empty policy will be created and stored. A future patch will move parsing out of FrameLoader::didBeginDocument into DocumentLoader::responseReceived so that we can begin doing some checks before a document is created. BUG=411889 Review URL: https://codereview.chromium.org/559503002 git-svn-id: svn://svn.chromium.org/blink/trunk@181811 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tkent@chromium.org authored
Only DatabaseManager::closeDatabasesImmediately could be called in non-main threads. However, it just calls DatabaseTracker::closeDatabasesImmediately(). This CL removes DatabaseManager::closeDatabasesImmediately, and only the main thread uses DatabaseManager. So, we can remove DatabaseManager::m_contextMapLock. We still need m_contextMap because the main thread can have multiple Documents. Oilpan: We can use PersistentHeapHashMap, and remove some |#if ENABLE(OILPAN)|. BUG=347902,397429 TEST=No new tests because of no behavior changes. Review URL: https://codereview.chromium.org/567453002 git-svn-id: svn://svn.chromium.org/blink/trunk@181810 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tkent@chromium.org authored
This CL merges - AbstractSQLStatement into SQLStatement - AbstractSQLStatementBackend into SQLStatementBackend - AbstractSQLTransaction into SQLTransaction - AbstractSQLTransactionBackend into SQLTransactionBackend - DatabaseBase into Database. 'Sync' versions of their subclasses were removed. These abstract classes are unnecessary. BUG=397429 TEST=none; No behavior changes. Review URL: https://codereview.chromium.org/561143002 git-svn-id: svn://svn.chromium.org/blink/trunk@181809 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
skyostil@chromium.org authored
This patch adjusts DrawingBuffer's behavior when a context is lost in two ways: 1. Always tell DrawingBuffer whether it is visible or not regardless of whether the WebGL context is lost. This is needed because visibility notifications may arrive from the browser while the context is lost and the compositor may also attempt to composite the DrawingBuffer during this time. 2. Don't check the current visibility in DrawingBuffer::prepareMailbox() if the DrawingBuffer is being destroyed. This is because the DrawingBuffer may become hidden right before the context is forcibly lost (using WEBGL_lose_context), and after that point WebGLRenderingContextBase no longer has a reference to the DrawingBuffer to update its visibility state. BUG=411372 TEST=Added in https://codereview.chromium.org/560023002 Review URL: https://codereview.chromium.org/556303002 git-svn-id: svn://svn.chromium.org/blink/trunk@181808 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pgal.u-szeged@partner.samsung.com authored
Removed unused threading/os code from tool/main.py and tool/mocktool.py. BUG=None Review URL: https://codereview.chromium.org/563533002 git-svn-id: svn://svn.chromium.org/blink/trunk@181807 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
nhiroki@chromium.org authored
This enables and tweaks ready.html to follow up the implementation changes. 1) Blink: https://codereview.chromium.org/476043002/ 2) Chromium: https://codereview.chromium.org/477593007/ 3) Blink: THIS PATCH BUG=399533 TEST=run_webkit_tests.py --debug http/tests/serviceworker/ Review URL: https://codereview.chromium.org/532653002 git-svn-id: svn://svn.chromium.org/blink/trunk@181806 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rune@opera.com authored
Schedule an invalidation set for :empty on an element when the pseudo state changes instead of a SubtreeStyleChange. R=chrishtr@chromium.org,esprehn@chromium.org BUG=412999 Review URL: https://codereview.chromium.org/565493002 git-svn-id: svn://svn.chromium.org/blink/trunk@181805 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mkwst@chromium.org authored
We're currently performing mixed content checks based on Resource::Type, which isn't granular enough to support the behavior specified in the mixed content specification (hence the introduction of the MixedContentBlockingTreatment enum). This patch introduces a new static mixed content checking method based on WebURLRequest::RequestContext, which will allow us to remove most of the complexity of MixedContentChecking in future patches. BUG=411184 Review URL: https://codereview.chromium.org/537983002 git-svn-id: svn://svn.chromium.org/blink/trunk@181804 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
kozyatinskiy@google.com authored
ExecutionContextClient was introduced in https://codereview.chromium.org/27311002. Now it isn't used. R=vsevik@chromium.org Review URL: https://codereview.chromium.org/559553002 git-svn-id: svn://svn.chromium.org/blink/trunk@181803 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tyoshino@chromium.org authored
Since Blink 175446 https://src.chromium.org/viewvc/blink?revision=175446&view=revision we're loading data into a file. The downloadToFile flag is determined in createRequest() i.e. inside xhr.send() call. But responseType is allowed to be changed even after xhr.send() call. Accumulate data into m_binaryResponseBuilder and create a Blob from it anyway if m_downloadingToFile is not set. BUG=412704 Review URL: https://codereview.chromium.org/562563003 git-svn-id: svn://svn.chromium.org/blink/trunk@181802 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rune@opera.com authored
Left-over from the removal of diffNeedsRecompositeLayer [1]. [1] https://codereview.chromium.org/360103008 R=abarth@chromium.org Review URL: https://codereview.chromium.org/565583002 git-svn-id: svn://svn.chromium.org/blink/trunk@181801 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
svillar@igalia.com authored
After r164062 percentages of indefinite sizes were correctly computed to "auto". The problem is that we were not doing it when the percentage was inside the minmax() function. In those cases it should compute to min-content for the min track sizing function or to max-content for the max track sizing function. Added a couple of tests, one to verify that we do not assert with percentages inside minmax() and another one to verify that we properly compute the percentage of indefinite size in various situations. BUG=401477,409085 Review URL: https://codereview.chromium.org/450093004 git-svn-id: svn://svn.chromium.org/blink/trunk@181800 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rune@opera.com authored
ElementRareData::resetStyleState() cleared the StyleAffectedByEmpty flag before recalculating style for an Element. However, this flag can be set by style recalc for any of the sibling subtree elements in the presence of adjacent combinators. If you have a LocalStyleChange for the element that may become empty/non-empty, the flag can not be cleared since it may never be set again unless the siblings affected by the :empty state are recalculated. R=esprehn@chromium.org BUG=412950 Review URL: https://codereview.chromium.org/558333002 git-svn-id: svn://svn.chromium.org/blink/trunk@181799 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
mkwst@chromium.org authored
Revert of Revert of Mixed Content: Move subframe checks into ResourceFetcher. (patchset #1 id:1 of https://codereview.chromium.org/550083003/) Reason for revert: This wasn't the root cause of the non-V8 context call. Original issue's description: > Revert of Mixed Content: Move subframe checks into ResourceFetcher. (patchset #2 id:40001 of https://codereview.chromium.org/544573002/) > > Reason for revert: > calls V8 from a non-V8 context > > Original issue's description: > > Mixed Content: Move subframe checks into ResourceFetcher. > > > > Currently we're checking for mixed content when loading the main > > resource of subframes in two places: DocumentLoader and ResourceFetcher. > > The former properly checks against the frame's parent frame, while the > > latter bypasses the checks entirely by virtue of the request's > > 'Resource::Type' being 'Main'. > > > > This is both confusing and difficult to replicate when moving to the > > brave new world of request contexts and frame types that Fetch now > > defines. > > > > This patch drops the DocumentLoader check, and moves the relevant > > logic into ResourceFetcher::canRequest and > > ResourceFetcher::checkInsecureContent. > > > > BUG=400087 > > > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=181383 > > TBR=mkwst@chromium.org > NOTREECHECKS=true > NOTRY=true > BUG=400087 > > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=181543 TBR=jochen@chromium.org NOTREECHECKS=true NOTRY=true BUG=400087 Review URL: https://codereview.chromium.org/559333002 git-svn-id: svn://svn.chromium.org/blink/trunk@181798 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
caseq@chromium.org authored
This just moves code from sdk/TracingModel.js to timeline/TracingModel.js and renames the former to sdk/TracingManager.js. No actual code was harmed. BUG=412709 Review URL: https://codereview.chromium.org/563463003 git-svn-id: svn://svn.chromium.org/blink/trunk@181797 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
jl@opera.com authored
By assuming that the |value| expression throws exceptions via the ExceptionState object, and only via it, we can skip the v8::TryCatch declaration and check. This is good since it is less code, and since v8::TryCatch objects cost a bit of CPU time to initialize. The correctness of this patch depends on https://codereview.chromium.org/559553003/ and https://codereview.chromium.org/556273003/ that make sure all type conversion helpers with an ExceptionState& argument actually throw all exceptions via it. Review URL: https://codereview.chromium.org/552143004 git-svn-id: svn://svn.chromium.org/blink/trunk@181796 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
pdr@chromium.org authored
As discussed on blink-core-owners-discuss, Kouhei should be an owner! TBR=kouhei Review URL: https://codereview.chromium.org/553773003 git-svn-id: svn://svn.chromium.org/blink/trunk@181795 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
loislo@chromium.org authored
plugins/touch-events-details.html plugins/transformed-events.html They were regressed by jdduke@ at #294250 (dd03ea64) BUG=413098 TBR= jianli@chromium.org, jdduke@chromium.org, NOTRY=true Review URL: https://codereview.chromium.org/564673002 git-svn-id: svn://svn.chromium.org/blink/trunk@181794 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
horo@chromium.org authored
http://fetch.spec.whatwg.org/ https://github.com/whatwg/fetch/commit/a898f9a2941350aa625aa79b24673628ac2b2a8e Request.body and Response.body is removed from the spec. Body interface is introduced. interface Body { readonly attribute boolean bodyUsed; Promise<ArrayBuffer> arrayBuffer(); Promise<Blob> blob(); Promise<FormData> formData(); Promise<JSON> json(); Promise<ScalarValueString> text(); }; Request implements Body; Response implements Body; BUG=411743,410197,410196 TEST=http/tests/serviceworker/ http/tests/local/serviceworker/ Review URL: https://codereview.chromium.org/555443002 git-svn-id: svn://svn.chromium.org/blink/trunk@181793 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tkent@chromium.org authored
BUG=123896 Review URL: https://codereview.chromium.org/561673002 git-svn-id: svn://svn.chromium.org/blink/trunk@181792 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tyoshino@chromium.org authored
This CL adds internalAbort() call to handleDidCancel(). This is not harmful. It's rather good that we clear resources. R=yhirano,sof,kouhei BUG=406229 Review URL: https://codereview.chromium.org/490083002 git-svn-id: svn://svn.chromium.org/blink/trunk@181791 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
tkent@chromium.org authored
Intent to remove: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/SYlD0YVUnQk Remove all *Sync interfaces and implementations, and WorkerGlobalScope:: openDatabase. CLs to simplify code follow. BUG=397429,323858,310866,357427 Review URL: https://codereview.chromium.org/561093003 git-svn-id: svn://svn.chromium.org/blink/trunk@181790 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
ojan@chromium.org authored
The only functional difference is that we no longer repeat the step name on every line. Otherwise, it's all CSS tweaks. NOTRY=true R=michaelpg@chromium.org Review URL: https://codereview.chromium.org/553343002 git-svn-id: svn://svn.chromium.org/blink/trunk@181789 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
sunil.ratnu@samsung.com authored
RenderFlexibleBox has several methods that take pointers to RenderBox instances but those methods assumes that the objects will never be NULL. We should replace them by references. This makes the caller code safer. Review URL: https://codereview.chromium.org/555213002 git-svn-id: svn://svn.chromium.org/blink/trunk@181787 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-
rbyers@chromium.org authored
This has been an alias for innerNode with a "remove this" FIXME for some time. The cleanup is pretty easy. BUG= Review URL: https://codereview.chromium.org/476303002 git-svn-id: svn://svn.chromium.org/blink/trunk@181786 bbb929c8-8fbe-4397-9dbb-9b2b20218538
-