From 9d097e7d1570d68e5fe77ff01595cf14a3e2cc29 Mon Sep 17 00:00:00 2001 From: Aneesh Agrawal Date: Thu, 9 Jun 2016 07:01:24 -0400 Subject: Use fn pipeline_id consistently, not fn pipeline Consistently use the name 'pipeline_id' to refer to a function that returns an (optional) PipelineId. This was prompted by discovering both fn pipeline and fn pipeline_id doing the same job in htmliframeelement.rs. Note that there is fn pipeline in components/compositing/compositor.rs, but that actually returns an Option<&CompositionPipeline>, not any kind of PipelineId. --- components/script/dom/storage.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'components/script/dom/storage.rs') diff --git a/components/script/dom/storage.rs b/components/script/dom/storage.rs index 7827cdb6b15..411e304b2f5 100644 --- a/components/script/dom/storage.rs +++ b/components/script/dom/storage.rs @@ -206,7 +206,7 @@ impl Runnable for StorageEventRunnable { assert!(UrlHelper::SameOrigin(&ev_url, &it_window.get_url())); // TODO: Such a Document object is not necessarily fully active, but events fired on such // objects are ignored by the event loop until the Document becomes fully active again. - if ev_window.pipeline() != it_window.pipeline() { + if ev_window.pipeline_id() != it_window.pipeline_id() { storage_event.upcast::().fire(it_window.upcast()); } } -- cgit v1.2.3