You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found matchingUrls (which is the mechanism used by vimperator to implement plugins' autoload) is really not a good idea to autoload plugins. See #117
In the dynamic websites, http servers will use route to select which pages should be rendered. So URL does often not direct a static file.
For example, https://github.com///blob///.pdf will not direct a PDF file. Github will open a webpage with its own online pdf reader to display this PDF file. So PDF.js will not be loaded by FireFox.
But https://raw.githubusercontent.com/////.pdf will response a PDF file via HTTPS. The media type of its HTTPS response is application/pdf. So FireFox will load PDF.js.
I think there are two potential solutions:
Use HTTP header matching (not url matching) to autoload. We can match different mediatype.
Use DOM detecting to autoload. Plugin authors need to define DOM detectors like ftdetect in vim.
The text was updated successfully, but these errors were encountered:
I found matchingUrls (which is the mechanism used by vimperator to implement plugins' autoload) is really not a good idea to autoload plugins. See #117
In the dynamic websites, http servers will use route to select which pages should be rendered. So URL does often not direct a static file.
For example, https://github.com///blob///.pdf will not direct a PDF file. Github will open a webpage with its own online pdf reader to display this PDF file. So PDF.js will not be loaded by FireFox.
But https://raw.githubusercontent.com/////.pdf will response a PDF file via HTTPS. The media type of its HTTPS response is application/pdf. So FireFox will load PDF.js.
I think there are two potential solutions:
The text was updated successfully, but these errors were encountered: