SmartCookieWeb: [Bug] SmartCookieWeb v12.x bugs
Describe the bug
Downloads and History pages bugs:
- 1. [Fixed in d0ecf00]
The downloads and history pages have the header in white in dark mode - 2. [Fixed in 1ac8c9a]
It is not possible to remove items from history by the page itself (This has probably just not been implemented yet) - 3. [Fixed in 1ac8c9a]
The arrow to return to the previous page does not work on the history page
Reading mode bugs:
- 1. It is now a little slower (both to enter and to use its options) if the page has too much text. Pages with lots of text can also crash SCW
- 2. [Fixed in 9268006]
It is not possible to remove downloaded pages in reading mode (This has probably just not been implemented yet)
Device Info
- Device: Redmi Note 4
- OS: [e.g. MIUI 11 (Android 7.0)
- App version: v12.0.0
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (13 by maintainers)
Thanks, I’ll work on fixing these in time for the next beta update next weekend.
@RickyM7 Thanks, I’ll try that when I finish my chores here.
Yeah, I still want to fix the reading mode slowness - I think that the device is having to load the entire text of the page even when some is offscreen, and that combined with rendering the links and formatted text causes a slowdown, so maybe in the next beta I’ll split the page into paragraphs and only load each paragraph when it’s on screen.
@RickyM7 I had accidentally referenced other issues by using the “#” symbol.
As for my issues, do you have “Clear History on Clear” enabled in “Privacy and security settings”?
I’m may be that this setting is not functioning properly (possibly triggered by false positives), since I have been making use of this setting since there Lightning Browser days, and only in the last few versions (since at least version 10) of SmartCookieWeb these issues have been cropping up.
No worried about the language, English isn’t my native tongue either, however due to living in the US during part of my childhood, plus translating and proofreading here and there, I’m proficient enough that I could usually explain what I meant (at least linguistically).
@RickyM7 Thanks, I’ll so so. And I’m sorry about the accidental cross-references, I’m used to using the sharp sign and I am currently glide typing from the Razer Phone with the same hand I am using to hold it.
Seems to be because the browser thinks they’re OAuth links. I’ll fix this in v12.1 later this week.