Skip to content
This repository was archived by the owner on Mar 13, 2018. It is now read-only.

Maybe fixes #207? Force upgrades before highlighting.#254

Open
arthurevans wants to merge 1 commit intomasterfrom
pec-207
Open

Maybe fixes #207? Force upgrades before highlighting.#254
arthurevans wants to merge 1 commit intomasterfrom
pec-207

Conversation

@arthurevans
Copy link
Contributor

The Polymer.dom.flush() call should force any pending upgrades to complete, meaning that the prism-highlighter should be attached before we fire the highlight events. See the bug description in #207 for analysis of what we think's going on here...

Also, use Polymer.dom() correctly. Existing code was calling scopeSubtree instead of doing the right thing.

@arthurevans
Copy link
Contributor Author

Unfortunately, this issue is intermittent, and I haven't found any reliable way to reproduce it. Assuming this patch doesn't make anything worse (so far as I can tell, it doesn't), perhaps we could roll it out for a while and ask folks to keep an eye out for this problem.

@arthurevans
Copy link
Contributor Author

More "correct" fix here would be to rework the racy connection between the guides page and the highlighter element. For example, have the prism-highlighter element fire an even on attached, upon receipt of which page retries the highlight request. Or, just have the page call a method directly on the element.

Better long-term fix might be to doing highlighting as a build step or on the server-side instead of offloading to the client.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant