Switch to disable picture-in-picture / video popout icon
-
@Ayespy
if PiP_toggle !false {
display PiP_button }Wow that's pretty complicated work there. Hopefully they can figure it out in another month's time.
-
"And everyone will begin to shun the forums because of all the negativity."
And your users will shun Vivaldi for being treated like garbage.
-
@beyondwudge Vivaldi is far and away the most customer-responsive software company I have ever seen. It's impossible to make everyone happy, but they must manage their time and efforts in a way that optimizes their productivity. I'm sorry it doesn't feel right to you.
-
@biguglyboy6 It's not being tweaked, tinkered with or patched. It is being rewritten. From the ground up. When it is released again, perhaps you will be happy with it. Perhaps not. In the meantime, it is also possible that the guy who is doing the rewrite will take a break from that to make some small adjustment. Or maybe if he gets a spare moment or two he will spend that on addressing one of the hundreds of bugs that the intake of Chromium 81 introduced. That's an all-hands effort typically, each time Google pulls the rug out from under Vivaldi again (every six weeks or so).
-
I might be outdated as my last programming experience is from back in the day in pascal, however implementing simple clause of "if checkbox then skip processing this whole block of code" is something that doesn't require 2 weeks of rewriting. This could've been fixed within an hour of first complaint, but it wasn't and still isn't - that is the issue now.
This whole debate metastasised into an issue of breaking users trust. It is no longer about only the PiP. What's next feature you plan to ram down our throats without option to turn off in the future?
A switch to disable a functionality should be the very first thing you program when adding new functionality. Period. You can't afford to treat your userbase like the tech giants sitting on the heaps of money do, ie not care about us at all. Your userbase makes you. Never forget that. You do not know best what we want. We do. That's why we use Vivaldi and not Chrome.
-
@Ayespy
It looks like none of you understand our complains. Really, I can't see why it's so hard.We all understand that fixing things take time. We all understand that Vivaldi has a small team. We only have asked, since the very first stable release, to put a damn turn of switch into the Settings ASAP. It should not take a month and the work of a dozen people to implement it.
Either it's being prevented to appear int he DOM, or just hidden via CSS, whichever is more simple. It's just a temporary fix.
So can you stop posting about how small the team is and how much work is it to to rewrite the feature?
-
@pafflick
You did not. His initial offensive comment is still visible. -
@sammael
That's what I've been talking about. -
Okay, not watching this topic anymore. I don't like the whole PIP thing either but they way people here are whining about it (I can't describe it any other way) is really not okay. Vivaldi team is small, it's not like a Google team. They have their reasons like they explained. It will be implemented but it takes some time. Live with it or use another browser.
-
@Nekomajin That's correct, I've decided not to take any arbitrary actions regarding that first post for now. If you feel that this is unfair, you can contact one of our Community Managers via PM, although I believe that one of them will soon take a look at this anyway.
But for now, I'm once again asking you not to discuss this issue here any further. I'm sorry for the inconvenience and I'm hoping for your understanding. -
@Nekomajin I don't think this is DOM or CSS. It does not seem to be exposed at /opt/vivaldi/resources/vivaldi/style/common.css (Ubuntu), which is where I would look for a workaround if I wanted to override the style both for my own pages or as a kludge for my own browsing. Something really weird is going on, like hardcoded-on-the-player-itself weird. I wanted to check the source code and make a diff from before and after the icon implementation, but somehow https://vivaldi.com/source/ does not include the latest version as of now...
-
It is sad we have to ask for this simple switch
-
Google didn't pull the rug out under Vivaldi on this one and this is why I think people are not happy with the amount of time it is taking the developers to address this. As I mentioned before, watching (YT) videos is one of the most important use-cases for a browser. Nobody wants to temporarily switch to a different browser and there are just a number of use-cases that have to work all the time. There are more options than just rewriting the entire code. What people expect is for the devs to simply pull the entire feature and release it when it's fixed. Telling us that "the guy might take a break to make some small adjustments" or "work on one of the hundreds of bugs that the intake of Chromium 81 introduced" isn't reassuring at all. Would be very surprised if multiple people within the Vivaldi team haven't already suggested to simply pull the feature. The only motivation I can think of is the concern that if people can disable it now, odds are that they will keep it disabled. Nobody likes to introduce a feature that way, you want them to experience the feature in a working state. Believe that giving us the option now would have been better. This is just making us worry about future bugs. Also no need to worry if most people don't find this bug that annoying. Understand that this isn't something that the team wants to share here on the forum, but without that discussion the disconnect with the community will remain.
-
@noroots I think the reason for not releasing a new Stable build that simply disables the feature would be that it would result in a whole new storm-in-a-teacup about why a useful feature (for those who use PiP) was removed.
The reason for not releasing a Stable build with an option to disable it may be that it makes more sense to do it in the Snapshot first and make sure that it works before releasing it in Stable (clearly something that they should have done in the first place).
It seems to me that most noise is coming from those who do not use PiP at all, or only rarely. Those who do use it are glad to have it, even if it is still unpolished.
-
@noroots I discussed this with Jon today - and the issue is more complex than you think. But it is being handled. And issues like this cannot be allowed to cause us to fall behind Chromium in the release schedule. Staying on top of Chromium updates is not job 1, but is is for sure job 2 at worst. Everyone knows how upset you are. I mean everyone. You are at this point beating a dead horse. It is being remedied as quickly as possible. You arguing with me improves exactly nothing.
-
@Pesala said in Switch to disable picture-in-picture / video popout icon:
It seems to me that most noise is coming from those who do not use PiP at all, or only rarely.
I guess majority of the users don't use it and don't care about it. It will be interesting to see some statistics.
-
@Pesala that's what I was thinking ā remove the feature (that's the easy part, just undo the git commits that added it), take as much time as needed to add the setting, rewrite it from scratch, patch chromium or whatever, and re-release it when it's ready for everyone. And make it disabled by default.
And, yes, it'd be interesting to know the percentage of users who actually use PiP. In my world it's this gimmicky feature with novelty that wears off in a week.
-
@Ayespy don't have to work in IT (which I do) to know that pulling a feature isn't that complex. I know enough. Good luck with everything.
-
@noroots I think you'll find that features may be pulled between versions, but not within a single version release cycle. Features have been pulled before, and will be again. Probably not on a particular version number while it is in the wild, though.
-
@Pesala
Two snapshots without a turn off switch...