Seems your desire to code Brave is for you not for the people using it. STOP closing topics without a resolution. If we took the time to key up problems or recommendations you could at least respond with a written response as to when the whatever will be addressed including a date of resolution. It’s time to be accountble and let’s get a voting leaderboard of enhancements like tab groupings that did nothing but take up space. Repairs always have top priority over enhancements. The users will vote modifications or features up or down rather than this haphazzard never knowing what’s getting done.
Topics that don’t receive any activity or replies for 30 days are automatically closed for inactivity.
Topics are sometimes closed manually by support team or mods for a variety of reasons.
Typically the flow here is that if there are issues that are not user specific (that is, they reproduce for a number of other users and they are not related to specific system setup/extensions/etc.), an issue will be opened on our Github for our developers to review and address when they are able. Note that you [anyone] are also welcome to submit a bug/issue on our Github directly as well.
Users already can vote on feature requests here in the Brave Feature Requests category. Support and devs do review and use these as general guidelines for seeing what users want in the browser. That said, it simply can’t be guaranteed that a feature request will be implemented. Further, even if it is something that we want/can/plan on implementing in the browser, we cannot make guarantees on when it will be implemented.
This is because software development is a complicated process. Features, fixes, additions, refactors get moved around, pushed back, pushed forward or sometimes outright canceled due to the frequently shifting priorities, requirements and developer bandwidth. This is true for all software development.
The Github Project board is a good resource to use to see where certain features are with respect to priority and status of work done.
As for your issue, you did not provide a ton of information to go off of and as such I’m not entirely clear on what you’re seeing.
If I understand correctly, you’re saying that if you have dark mode enabled – which I’m assuming you mean the Enable force dark for web contents – and you go to print a page, the print preview shows that it’s going to print the page background color as well, which would be black?
If that is correct, then this already happens. For example if I go to print this Wikipeida page in dark mode, the preview shows the page as white and will print white, as intended:
If I am not understanding the issue correctly, then we’ll need you to provide some additional details/information about your issue so we can better assist you.
And to amend, like this forum, it will try to print dark (using the forums own dark mode, no forced modes), but you can uncheck the background checkbox, and it makes it lighter on your toner/ink.
There are solutions to issues, and when there aren’t, patience is always a must.
Precisely true.
As for their original post which mentioned screenshots: There’s nothing you can do there, it’s a “screen” shot, so how it’s rendered on-screen is what the screen shot will contain. You can invert the colors in an image editor (but if it has faces of people it’ll look like a negative), or temporarily disable the websites dark mode for screenshots.
So you’re keeping two lists. One on here and one on Github. But that doesn’t address that me or someone else has taken time to document typically a problem and you’ve closed it because 30 days have passed. You think that people that spend their time writing this stuff up only to have some system function come along and close it feel appreciated? Guess what most will never do again? OK so maybe it doesn’t get to the level of an implementation date but it should at least be addressed from a functional standpoint and put into the work queue. If you want to close it then explain to the person that explain why it doesn’t fit into “the vision”. Just because someone has written it up doens’t mean that any of us that would support it have seen it. We’re all busy but you have access to the requests and maybe you need to send a report to everyone that’s willing to take the time to rank the changes rather than random access will find the audience.
I’ve done software development for my entire life you telling me that it’s complicaed doesn’t provide and solution to anything it’s just one of the things people say to talk down to people. It’s too complicated for your head. BS
The link you referenced in your repsonse to me was outdated. Ha. I guess they do the same thing you do. If I say Dark Theme I mean Dark Theme. To me this is a problem that any one using a dark theme knows because there was 33 people that looked at it but of course no resolution. If you want to disable posts then you need to alert the OP that they have a week to update their post. YOU are ultiamtely the one that closes them no one else can nor can we rectivate them. There are 3 choices all better than what you’re doing now.
If you didn’t understand the dark theme print problem then rather than supply an off-boardresoltuiion maybe you should have asked a question.
I’ll glady go on regarding this topic but let’s see how you respond to this. I’m not gonna waste my time which is what this 30-day solution does is wastes my time because you don’t take it seriously.
@CityguyUSA I’m not particularly interested in continuing to argue over how to manage the Community. I appreciate the feedback regardless.
If you want assistance with your issue, I’m happy to help with that but if you aren’t willing to help with the troubleshooting process then there isn’t anything I can do for you. I cannot see your screen or know anything about your setup without you providing that information.
As you’ve done software development for your entire life, you should know more than most that it is important to be clear and specific about issues you’re reporting. It’s the reason we include the template in the editor so that we don’t have to go back and fourth with users in order to get basic information surrounding the issue/setup. As such, it is important to clarify whether which “dark theme” you’re referring to. I have had many instances of users saying “Dark theme” when what they really mean is the experimental “Night mode” and vice versa.
Further, in your original issue, you tagged it with every OS – so I am not able to test and reproduce the issue (as I understood it) on my end because I don’t know which platform you’re seeing the issue on.
The topic was viewed 33 times – this does not mean each viewer had the same issue as you.
Well I did:
I then further illustrated that I’m not seeing what you’re seeing (as I understand it).
Again, I’m happy to help you resolve this issue if you’re willing to work with me/us and can provide the information relevant to your issue. At this point, it may be easier to open a new thread here on Community so we can start fresh. I’ll let you decide how to move forward.
