Revision history [back]
 | 1 | initial version | posted 2014-02-06 08:57:57 +0200 |
Accessing wired.com shows
When avcessing wired.com using the native sailfish browser, the url xhanges to something like
wyciwyg://0.0.0.3/http://www.wired.com/
The URL scheme is used internally by gecko as far as I understand the according wikipedia entry. The side itself is unusable.
It looks as if there is an issue with caching that is exposed by accessing this side.
I have not encountered it anywhere else so far.
| | 2 | No.2 Revision |
[Bug] Accessing wired.com showsshows wyciwyg:// URL scheme
When avcessing wired.com using the native sailfish browser, the url xhanges to something like
wyciwyg://0.0.0.3/http://www.wired.com/
The URL scheme is used internally by gecko as far as I understand the according wikipedia entry. The side itself is unusable.
It looks as if there is an issue with caching that is exposed by accessing this side.
I have not encountered it anywhere else so far.
| | 3 | No.3 Revision |
[Bug] Accessing wired.com shows wyciwyg:// URL scheme
When avcessing accessing wired.com using the native sailfish browser, the url xhanges changes to something like
wyciwyg://0.0.0.3/http://www.wired.com/
The URL scheme is used internally by gecko as far as I understand according to the according wikipedia entry. The side site itself is unusable.
It looks as if there is an issue with caching caching, then that is exposed by accessing this side.site.
I have not encountered it anywhere else so far.