This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27975 - [Custom]: No way to unregister a component
Summary: [Custom]: No way to unregister a component
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on: 24578
Blocks: 14968
  Show dependency tree / graph
 
Reported: 2015-02-07 18:40 UTC by Randy Harmon
Modified: 2015-07-06 08:05 UTC (History)
4 users (show)

See Also:

Attachments

Description Randy Harmon 2015-02-07 18:40:51 UTC 
When writing unit tests, I'd like to be able to unregister a component, so that I can test various scenarios of the registration process.  The spec doesn't deal at all with removal of custom elements.

I'm writing code that actually performs element registration depending on backbone configurations, if that helps with context.
Comment 1 Dimitri Glazkov 2015-02-07 18:54:44 UTC 
I think the solution is in being able to create/discard registries. See bug 24578.
Comment 2 Olli Pettay 2015-02-07 19:01:04 UTC 
Would using separate iframes be enough for testing?
Comment 3 Elliott Sprehn 2015-02-08 02:00:15 UTC 
(In reply to Olli Pettay from comment #2)
> Would using separate iframes be enough for testing?

Yes, existing test frameworks use iframes.
Comment 4 Dimitri Glazkov 2015-02-08 02:03:25 UTC 
https://github.com/Polymer/web-component-tester
Comment 5 Hayato Ito 2015-07-06 08:05:44 UTC 
Moved to https://github.com/w3c/webcomponents/issues/152