Recension av Arioch
Betygsatt 3 av 5
av Arioch, för ett år sedanThe idea is great, but the implementation suffers a lot.
Other users say: For some reason it enforces music.youtube as mobile website
This is NOT limited to YT though. Russian e-shop ozon.ru is affected as well.
Whenevet i click any link in the shop user account it is open in mobile view instead of normal! I had to click RELOAD after every navigation.
I don't know what variables are set, cookies, or WebSQL or WebStorage or anything else - but probably the extension makes them polluted.
It is said, that "by default side view opens mobile rendering" but!
1. WHY is it rendered, wasting my traffic, memory and CPU, when the side view is CLOSED ?
2. WHY does it leaks its mobile state to the main tab?
3. WHY is it rendered BEFORE main tab, instead of AFTER ? Common sense says the side-view is a mobile ghost of desktop pages, then they should follow as wingmen, not lead as commanders!!! That would have also concealed (not fixed, but concealed at least) the leaking state error.
Had to disable it. Unsable. Pity, because the diea is great!
P.S. feature suggestion, the Opera (original one, not Chrome skin) had a "attached window" feature, guess it was CTRL+J by default. That side-by-side window was showing all the links in the current page, in a simple list, flat or idented. This could be a helpful and lightweight added mode to the extension. It arguably could have more use for generic users than heavy and intrusive mobile view.
Other users say: For some reason it enforces music.youtube as mobile website
This is NOT limited to YT though. Russian e-shop ozon.ru is affected as well.
Whenevet i click any link in the shop user account it is open in mobile view instead of normal! I had to click RELOAD after every navigation.
I don't know what variables are set, cookies, or WebSQL or WebStorage or anything else - but probably the extension makes them polluted.
It is said, that "by default side view opens mobile rendering" but!
1. WHY is it rendered, wasting my traffic, memory and CPU, when the side view is CLOSED ?
2. WHY does it leaks its mobile state to the main tab?
3. WHY is it rendered BEFORE main tab, instead of AFTER ? Common sense says the side-view is a mobile ghost of desktop pages, then they should follow as wingmen, not lead as commanders!!! That would have also concealed (not fixed, but concealed at least) the leaking state error.
Had to disable it. Unsable. Pity, because the diea is great!
P.S. feature suggestion, the Opera (original one, not Chrome skin) had a "attached window" feature, guess it was CTRL+J by default. That side-by-side window was showing all the links in the current page, in a simple list, flat or idented. This could be a helpful and lightweight added mode to the extension. It arguably could have more use for generic users than heavy and intrusive mobile view.