This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Would be good to have the magic popups on <dfn> elements be precomputed. This would allow for: - the links to work on the multipage spec - the IDs to be real IDs, not generated by the dfn popup logic - the links to the mentions to themselves use the embedded content logic that gets added for bug 25744
(In reply to Ian 'Hixie' Hickson from comment #0) > Would be good to have the magic popups on <dfn> elements be precomputed. > This would allow for: > - the links to work on the multipage spec > - the IDs to be real IDs, not generated by the dfn popup logic > - the links to the mentions to themselves use the embedded content logic > that gets added for bug 25744 Big +1 to adding this. At one time I wrote a patch for the spec splitter that made the dfn links work in the multipage output. But the performance of it sucks, and anyway the splitter is the wrong place to do it. Maybe it should be done in anolis instead? Or in some separate single-purpose script, to keep things simple. Anyway, if you're not in a big hurry on this I can take a shot at writing something up for it in python -- either as a patch to anolis or as as separate single-purpose script. Lemme know. Of course if you end up getting to it before I can, I won't cry.
I'll be doing this as part of my new pipeline.
(In reply to Ian 'Hixie' Hickson from comment #0) > Would be good to have the magic popups on <dfn> elements be precomputed. > This would allow for: > - the links to work on the multipage spec > - the IDs to be real IDs, not generated by the dfn popup logic > - the links to the mentions to themselves use the embedded content logic > that > gets added for bug 25744 I wonder if we can move this issue to resolved=wontfix now that: - we do already now have IDs that are real IDs, not generated by the dfn popup logic - with https://github.com/whatwg/wattsi/pull/46 we will have wattsi generating the necessary data to make dfn links work across the multipage spec - the mechanism in https://github.com/whatwg/wattsi/pull/46 can be further refined to make wattsi also generate the data needed to resolve bug 25744 In other words, we can solve the problems above without needing to statically embed the dfn popups as this bug proposes. And it seems our current sense is that we would rather not embed the popups anyway—to avoid shifting the bandwidth etc costs over to users. Given that many (or possibly most) users don’t click on many dfn’s, it makes more sense to load each popup/data on demand only when a user clicks one.
I agree; let's consolidate this into the work to make dfn.js work on multipage, but not via statically-embedded popups.