Linkify Plus Plus

Based on Linkify Plus. Turn plain text URLs into links.

< Feedback on Linkify Plus Plus

Question/comment

wOxxOmMod
§
Posted: 2015-10-06
Edited: 2015-10-06

Links on dynamically parsed w3c pages are broken in Chrome after doing Back then Forward navigation

Using Chrome 47, TM3.12.4812:

  1. Go to https://github.com/w3c/netinfo
  2. Click Use cases and requirements on the bottom of the page
  3. Wait until the stupid async loader used by w3c reformats the page
  4. Observe the links after Table of contents look correct
  5. Navigate one step back in history
  6. Navigate one step forward in history
  7. Now the links after Table of contents are broken: [convenience sampling](http://en.wikipedia.org/wiki/Accidental_sampling)

Although this is apparently the fault of that ReSpec script w3c uses but I thought maybe it's worth adding an exception http://w3c*.github.io/* in the script itself? (I added it locally in Tampermonkey)

Another idea would be to catch the markdown like [title](url) and convert it into a proper link, but I doubt it's universal, because usually anyone dealing with raw markdown prefers seeing it as is.

eightAuthor
§
Posted: 2015-10-07

To catch markdown links sounds good. Maybe we can detect window.respecVersion then ignore the markdown url. (or even ignore whole page?)

Another way is to stop linkification until reSpec is done. I will check their documents these days.

eightAuthor
§
Posted: 2015-10-07

It's impossible to check respec state because w3c loads them asynchronously:

<script class='remove' src='//www.w3.org/Tools/respec/respec-w3c-common' async></script>

I will just add http://w3c*.github.io/* into excluding list.

eightAuthor
§
Posted: 2015-10-07

Fixed in 6.2.1

Post reply

Sign in to post a reply.