Skip to content
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.

uMatrix Functions Affected By Monitor Resolution #610

Closed
jputting opened this issue Aug 25, 2016 · 8 comments
Closed

uMatrix Functions Affected By Monitor Resolution #610

jputting opened this issue Aug 25, 2016 · 8 comments

Comments

@jputting
Copy link

jputting commented Aug 25, 2016

I am having an issue with the uMatrix Matrix popup being affected by using a monitor resolution 1024 X 576 which I choose to use because my eyesight isn't what it used to be.

For an example if I visit http://aca.nine.com.au/ playback of video is blocked and I need to make a few exceptions to get videos to play, But at this 1024 X 576 resolution the individual cells in the Matrix become unresponsive.

I have to manually adjust my monitor resolution to 1344 X 756 to make those needed exceptions and then restore it back to my preferred resolution when things are working properly.

This is quite an annoying issue because uMatrix is so useful and I don't wish to have to abandon using it because of this issue.

uMatrix 0.9.3.6 is installed in Firefox 48.0.1 and I'm using Mac OS X El Cpaitan 10.11.6

@Atavic
Copy link

Atavic commented Dec 27, 2017

Cannot you set static rules for that specific scope? If the links are dynamic you can create broader rules, up to nine.com.au

@jputting
Copy link
Author

This is an annoying bug in Umatrix which affects the user interface(UI) at any time you wish to use it to block or allow anything at all.

This is affects every website and it's a design flaw which would most likely require a redesign of the Umatrux user interface to correct.

Gorhill has NOT even bothered to acknowledge this bug is present even though I complained about this way back in August 2016. So the chance of this ever being fixed seems to be nonexistant.

It is seems very clear that he is NOT interested at all in fixing this even if Umatrix is not working properly when a monitor resolution is set a different resolution.

@gorhill
Copy link
Owner

gorhill commented Dec 28, 2017

@jputting uMatrix and uBO are not my day job, they are side projects. You could hire one or more contractors to fix the issues which are important to you.

@TriMoon
Copy link

TriMoon commented Dec 28, 2017

@gorhill , instead of such a reply you could acknowledge it and flag it appropriately.
Then when time comes, or others find a fix for it, you could patch it...
It will also prevent duplicate reports for this issue...

This kind of replies from you as the developer are just making users of this extension hostile....

@jputting
Copy link
Author

I completely agree with TriMoon, At the very least Gorhil should have acknowledged there is a fault and make people aware that he has a very full schedule for the foreseeable future.

This yet another example of the sheer arrogant, aggressive and attitude Gorhil adopts when anybody dare attempts to find find faults with his precious little side projects.

My parents always taught me that if something is worth doing it is worth doing properly to the best of your abilities or it's not worth doing it at all.

@gorhill
Copy link
Owner

gorhill commented Dec 28, 2017

you could acknowledge it and flag it appropriately

I went through a lot of bug sorting in this repo in the last weeks, and a lots of issues were closed. I did not close this one.

@gorhill gorhill reopened this Dec 28, 2017
Repository owner locked and limited conversation to collaborators Dec 28, 2017
@gorhill
Copy link
Owner

gorhill commented Dec 28, 2017

@TriMoon

This kind of replies from you as the developer are just making users of this extension hostile....

Please do not lecture me. My reply was perfectly appropriate given his comment:

It is seems very clear that he is NOT interested at all in fixing this

If you want to lecture because an issue has been left opened with no comment, you have your work cut out on GitHub where such issues abound (example) -- and there is nothing wrong with this: it does not mean the developers do not care.

Some people need to be reminded that they are using wholly volunteered code from GPL-licensed projects. Read carefully section 15 of the license, verbatim:

  1. Disclaimer of Warranty.

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

Lashing out at volunteer developers because they do not spend more time than they already do on their own volition is what is hostile.

The last thing I need on any given day is to have to deal with that sort of attitude of entitlement -- this just make visiting GitHub dreadful. I sure would have a had better day today without @jputting's unproductive comment which contributed nothing positive to the issue here or the project as a whole.

@gorhill
Copy link
Owner

gorhill commented Apr 15, 2018

Duplicate of #483.

@gorhill gorhill closed this as completed Apr 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants