getify/Mock-DOM-Resources

should we add a `markup` option?

Open

#8 aberto em 7 de abr. de 2017

Ver no GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (6 forks)github user discovery
help wanted

Métricas do repositório

Stars
 (26 stars)
Métricas de merge de PR
 (Métricas PR pendentes)

Description

Should we add an option that pre-configures the DOM (maybe just the head?) with elements as if they had been parsed from the markup?

Notably, some elements like <script async> behave differently if parsed in markup as opposed to being added via API calls in code. This option would allow you to mock out what the initial state of that part of the DOM was and have it behave as markup instead of API calls. It would go ahead and "request" any resource URLs from <script>, <link> or <img> elements.

This would then maybe become the preferred way to emulate markup <link rel=preload> elements over what's currently required: to artificially create those with DOM API calls. The timing would of course still be controlled by resources entries.

Guia do colaborador