-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Night mode: be always dark #57
Comments
Not really a bug, but a limitation. Yes, it can be improved. |
I see. I also noticed that scrolling too much also brings the brightness. |
You can try the improved night mode with this dev package! |
Will I still get updates from store after installing or do I have to notice the updates by myself? #54 still isn't fixed unless the fix just didn't come to that package. Night mode seems to work better with quick testing now, but if I zoom or go further from the page (two fingers to either direction) the whiteness comes. |
Yes, because is still 1.5-x!
I have fixed it in subsequent commits :)
That's a component issue, by default, WebView's background is white. I have released 1.6 in OpenRepos, you can download it from there or wait until it lands in the Harbour :) |
I see, I haven't followed version numbers so much. Odd for development even for stable? ZNC used that before.
I will probably wait, OpenRepos broke for me some time ago and even if I factory reset after that it's probably the best I don't use it unless I absolutely have to (Call Recorder). |
I'm using 1.x for the QtWebKit based browser and 2.x for the QtWebEngine one (hopefully)
Ok! |
Some pages also still start by loading themselves as white, I don't remember which exactly, but at least Dropbox FAQ (I was checking which ports it wants from firewall). This version is a lot better though. |
mobiili.fi had large white area when started from Communi Sailfish (IRC), but it disappeared by itself after some time. |
Some pages cause the screen to flash as white (when night mode is enabled which hurts eyes for example:
WebKit bug, I presume?
The text was updated successfully, but these errors were encountered: