Address pop up on lower left corner still annoying

[Pathduck]

I posted this in the huge topic back when this bug was introduced, apparently completely ignored by all the people tearing their hair out over this "terrible bug".

/* Temp fix for StatusInfo showing when StatusBar set to Hide */
.StatusInfo {
  display: none;
}

https://forum.vivaldi.net/topic/10549/guide-modding-vivaldi

Personally I can't for the life of me figure out why someone is not interested in knowing where the links they are clicking actually lead.
But, at least Vivaldi allows for a simple workaround while waiting for a fix.

[barbudo2005]

@Pathduck

Please do not minimize this bug. You cannot navigate with it.

[DoctorG]

@barbudo2005 Yes, the URL popup is a usability issue. Me too.

[Pathduck]

@barbudo2005 @DoctorG
I don't understand, please clarify why this is an accessibility issue and why you "can't navigate" with it.

All I see is that the popup appears even with the Status Bar set to Hide.
Which is a bug - but IMO not a major one.
Seems to be just an annoyance for people who don't like to see a popup showing the link target for some strange reason.
Something absolutely ALL browsers have by the way, and always have had, and it can't even be turned off in other browsers.
So people are getting angry about something all browsers do - and that Vivaldi actually allows you to hide, but temporarily is not working and can be easily worked around with simple CSS.

[DoctorG]

@Pathduck said in Address pop up on lower left corner still annoying:

I don't understand, please clarify why this is an accessibility issue and why you "can't navigate" with it.

Spatnav.
Usability.

[Pathduck]

@DoctorG Oh sheesh that's an edge case if I ever saw one!

You mean you can't see what element is chosen because of the popup, or that you can't press Enter on the link when the popup blocks it?

[DoctorG]

@Pathduck I can navigate but the tooltip should never cover focused element.
#WCAG #WAI

[DoctorG]

@Pathduck said in Address pop up on lower left corner still annoying:

Oh sheesh that's an edge case

Yes, i always find such

[barbudo2005]

@Pathduck

Sorry, I must learn to be less subtle in my sarcasm.

[Pathduck]

@barbudo2005 I are computer people, I not understand sarcasm, I only understand logic circuits beep bop beep

[brendajones]

Has this error been fixed yet? It pisses me off too.

[JoeyB1]

@Pesala If you have no answer to questions asked, and can only offer condescending replies, please just skip over my replies.

[JoeyB1]

@Pathduck You were not ignored, and appreciated for your help. Unfortunately it is beyond my skillset.

[Pesala]

@JoeyB1 There was no condescension in my replies. You asked when this bug would be fixed, and I told you the answer. The developers fix bugs when they have time, but they do not give any estimate of when any particular bug will be fixed.

It will be fixed when a developer has time and it reaches the top of the long list of things to be done.

All of us long-term forum members, moderators, and ambassadors do our level best to help users who are unfamiliar with the way that Vivaldi development works.

Pathduck not only offered you a simple workaround, he also gave you a link to the modifications forum where it explains how to apply CSS mods. It is not hard; I use dozens of such short code snippets, but have little idea how to write them. There are others who are expert in coding them. Just copy/paste their code once you have figured out where to put the custom.css file(s).

[JoeyB1]

@Pesala I see no designation of administration, Vivaldi team, moderator or similar, so I can only assume you are a Vivaldi user as I am. You gave no answer, no helpful suggestion/link as Pathduck provided, and only said what is already known. Then you felt the need to explain 'ETA' to me.
That is condescending.
So, I will repeat in case you missed it initially, If you have no answer to questions asked, and can only offer condescending replies, please just skip over my replies.
Thank you.

[Pesala]

@JoeyB1 Please stop lying that I gave no answer to your question.

You asked:

How soon for the fix?
So I answered your question. No ETA is usually given.

Then you asked again:

Maybe I should ask instead, when will the developer find the time to fix this issue?

What don’t you understand about “No ETA is usually given?”

I answered your question twice, just to be sure that you understood, but you refuse to accept the answer. Nobody knows when a bug will be fixed. Even the developers are not sure, which is why they don’t give an ETA.

[JoeyB1]

Which part of "If you don't know, please don't reply" don't you get?

[Pesala]

@JoeyB1 I do know the answer, so I replied.

Just skip my posts, or put me on your block list if you don’t wish to know the answer.

[Ayespy]

@JoeyB1 ETA's on fixes are never offered. Pesala's answer is correct. While he said no ETA is "usually" given, it's more than "usually," actually. It's "ever."

If you have a bug report in, you can request a status on the bug in the relevant topic, and you will be informed if the bug is confirmed, if anyone is assigned, and whether it is reported fixed. That is all.

Once in a blue moon, a developer may report on the forums that they are working on something, or if they have pushed a fix (internally) but no one will ever tell you when the fix will appear in a published version, because no one knows. The answer to "when?" is always "when it's ready."

I hope that clarifies the matter of how "How soon for the fix?" can be answered. It can't be answered.