Vivaldi 1.11 – Focus on accessibility
-
@Sparrows I think you're missing the point. A sense of proportion is needed.
With the small team available to both make new progress and fix old bugs, with the continual flood of changes in the underlying browser engine (Chromium) that creates new bugs with every release, with the thousands of existing bugs and the fifty to hundred bugs reported every single day (31 so far today, and there are many hours left in the day); it is unreasonable to expect any bug to be addressed within any particular time frame. You cannot assume any is major or minor, or easy or difficult to fix. You just have to report bugs as you find them, and then let the team do their best work every day, and wait for progress.
A single bug can take one developer all day, every day for multiple weeks to diagnose and fix. One such fix was just updated into the Stable version.
Bugs that kill everyone's browser experience and make the browser unusable for hundreds of thousands of users, of course receive first and fullest attention and, even when hard to fix, may get slain before "simple" ones are looked at. That would be a bug that is so important that it, figuratively, "has its own YourTube channel." Everyone is paying attention to it.
-
@Ayespy I can only hope that that this bug (https://forum.vivaldi.net/topic/16845/bookmarking-page-short-cut-doesn-t-work/5) gets squashed in the next release of Vivaldi.
-
@Sparrows Hope springs eternal...
-
Wow. Vivaldi is possibly and most probably the most sensible user-centric web browser I have ever seen. You take a no-compromise approach at giving the power and options to the end-user, which is how the Internet has been originally designed and how things should ideally be. I am blown away. Thank you.
-
@loloyd A lot of us see it that way. Glad you noticed! And to think it's probably only 50% of the way toward its ultimate user-centric goals...
-
I only use two clear-web browsers, Opera, and Neo-Opera!
So in effect, I really never left Opera as my main browser! -
I just downloaded 1.11, and my custom theme is messed up. The font color of the menu text and the words on the tabs is now white instead of black. I can't get it to change back to black. I can't make that edit to my custom theme, and I also can't start over with an included theme and redo it. No matter what I do, it insists on making the font color white. Can you help me?
-
@inclement The 2nd colour selector controls the text colour. Are you able to change that to black (#000000), or does it just revert back to white (#FFFFFF)?
-
@lonm Thank you for answering so quickly!
The second color selector ("Foreground") is currently and always has been set to #000000. It's just that after I upgraded, it doesn't appear as black in the browser, it appears as white.
Here's a screen clip, simultaneously showing the settings and the displayed color.
-
@lonm Did I goof up replying and mess up this thread?? Sorry...
-
@inclement Are you trying to say there's white text on a white background there? I appear to be clearly seeing black text (#000000). It you're talking about the text on the tabs, that appears to be a contrast judgment that Vivaldi makes. It will not allow you to have black text on a background that it thinks is too dark, and so it reverses it.
My setup does the same thing. It shows all foreground markings and text as black (#000000) except on my tabs, which are a dark color (#407630), and on those, it shows text as white. (Except the active tab, which is white, and so the text is black).
-
@ayespy He's referring to the "Vivaldi menu text" and "tab title text"
Could this be related to the "Apply Accent Colour To Window" setting which affects the squircle as explained :-
@atlemo said in Vivaldi 1.11 – Focus on accessibility:
@tbgbe: Themes using
Apply Accent Color to Windowwill get a monochrome version of the icon, in this case black (changes to white depending on luminecense). This is to make sure it's legible for all the possible background colors.Win: Snapshot Vivaldi 7.4.3671.3
-
@ayespy Yes, I'm talking about the text on the tabs, and also the menu headings. If it is making a contrast judgement, it wasn't doing that until I downloaded [more accurately, updated to] 1.11. I guess I think if we set up a custom theme it shouldn't override what we tell it...defeats the purpose of customizing...
-
@tbgbe Right. It doesn't matter what you set those to if the background color is too dark. The browser will show them as white. 1.11 does have new contrast settings - and it doesn't entirely defeat customization. It just errs in the direction of visibility. The effect can be reduced with slight color changes and with making sure that you do not have any enhanced contrast settings selected under Menu/Tools/Settings/Appearance /Color.
-
@inclement @Ayespy OK then, so a quick check for this "customisation problem" would be to turn off that "Apply Accent Colour to Window" setting to see the effect in your required theme?
-
@tbgbe I'm not entirely sure what that setting is intended for, but when I uncheck that box, it seems to swap the areas where the "accent" color and the "background" color are applied.
-
@ayespy @TbGbe @LonM Okay...deep breath, because I really don't want to yell at people, but there's a point to be made...do you see how this is aggravating? Make all the contrast judgements you want in the pre-defined themes. But customization shouldn't be defeated at all - it's customization. If someone wants the ugliest color combination on earth, they should be allowed to have it, and how does it hurt anything to let them?
Also, some of this is in the eye of the beholder. With my accent color of #aaaaaa, I actually think the white font color is less crisp and harder to read than the black.
Obviously that's just my opinion and others may disagree. But again, people should be allowed to do what they want in customization. "Overriding customization" is a contradiction in terms.
(Thank you for listening...)
[Added: I don't have any enhanced contrast settings selected under Setting/Appearance; it's set to "no modifications."]
-
@inclement I see were you're coming from, but you should consider that Vivaldi had to streamline the theming process. -- The fewest options possible with the widest impact. That this messes up your special case is unfortunate, but instead of complaining you could do something about it and just implement a custom modification.
Setting the text color of tabs is a really easy and fast mod. If you aren't willing to try this, you will have to wait for Vivaldi to implement an additional option to control the text color of tabs. But it's not that simple, because the color of tabs can change dramatically, if accent color from active page is activated -- who is gonna decide the text color then? Should it be written down for every possible tab background set by the application, determined by the user?
-
@inclement Your points are all valid. The one thing I can also say, with absolute certainty, is that the Designers and Developers responsible for that change had no intention of breaking your theme. The reason behind the change was to make something else better and any negative impact was unintentional.
For a quick fix, try changing your Accent colour to #acacac - it's only slightly lighter than what you had before but that should restore the black text.
The other thing that you can do is to file a bug report at https://vivaldi.com/bugreport/
Include your theme settings that worked well for you before, and pass on some friendly feedback. When you get a confirmation e-mail, reply to it and attach a copy of your screenshot. I don't think that they'll revert the change or come up with an immediate fix, but they definitely will take your feedback into consideration when they make future changes. -
@xyzzy Thanks for the #acacac suggestion - you're right, it did restore the black text.
I'll file the bug report sometime soon - and I do appreciate the simple recognition that this is indeed a bug, and unintentional.
