>Seriously, who submits feature requests with language like "the design must be changed" and "this is wrong?"
I don't know. Perhaps the awkward phrasing points to non-native speakers. I know a few people who phrase comments this way, and often they're just translating literally from their native language.
>The entitlement from some of the people in that thread is insane.
That is not a display of entitlement at all.
Users complaining about changes in a product that they do not like is a good thing and must be encouraged. If nobody says anything and just "takes it" things will stay the same. How much weight you want to give to those comments can be argued. Certainly much like in the case of restaurant reviews, a vocal minority can be negative, but you can take them with a grain of salt.
I think that explanation would be new edge cases for the risk of fullscreen sites impersonating the desktop?
When I worked on bugs I would always be careful to note that kind of reason even if I was a little too terse for the users.. I'd hate to see the motivated new hire try to improve ease of use by examining closed bugs like this one.
For example, open a new default tab--the one with a google search bar. Fullscreen it. Now try to enter a search. I get a "Please enter a URL" popup and the page is unusable. I maintain that "This default thing on your screen should not work and gives you an impossible instruction" is a weird design decision. https://code.google.com/p/chromium/issues/detail?id=533935
It wasn't just a "guy". Both the reporter and the closer are project members and committers of an open source project. pkasting could have at least provided some reasons why the feature request won't even be considered. Without any real counter points, maybe the "guy" does know better.
If you've been a dev, you know that users want all sorts of things. They are generally awful. Devs may have a long-term plan that they are executing to, or a design template they conform to, or any number of things the user doesn't know about. When users start listing chapter-and-verse how the product should work, its not helpful.
A real report would have said something like "No way to enter a url on fullscreen tab". That might have survived 'bug triage'.
Is surviving bug triage the responsibility of the bug finder or the development team? I expect developers (owners and experts of the software) to weed through the muck and understand the heart of the issue that they need to resolve...it's critical that developers not accept everything at written value.
Also the project is a Google project and isn't it the Dev responsibility to read, consider the features and bugs, yes users will always want more, but honestly they should sit back and think about this feature, I say that they all use Mac OS and in Mac OS you can enter URL on full screen tab :D
Anyways I shifted to firefox, also the dev who said "this is as per design", it is a huge irony that they work in the same org who made such a beautiful material design, I only wonder how Android would have looked had they taken such a careless approach regarding its "design"
apparently everything third party says is as per design and won't change, even if it is significant improvement and this feature makes sense and 500+ people have raised the same request, of course you don't listen to everyone but 500 people took time to upvote it so it is worth a look from the dev side also if all FOSS projects are going to be run like this then God help us.
>tl;dr: Guy thinks they know better than Google designers, and tries to dictate app behavior. Frustration results.
Are you serious?
Try using firefox in full screen mode and chrome in full screen mode on win or linux and you'll understand, and as far as dictating app behavior is concerned that is the whole point of open source right? If they think we all are trash then why open source it? just for namesake?
Same feature is available in FF and IE since centuries, apparently the designers of FF and IE were idiots then
Good god. That thread makes me want to smack myself upside the head.
Unmoderated bugtrackers for open source projects only worked when the people who knew about them were a self selecting group. It's becoming clear that a new model is going to be needed.
15 comments
[ 2.8 ms ] story [ 55.0 ms ] threadThe entitlement from some of the people in that thread is insane.
I don't know. Perhaps the awkward phrasing points to non-native speakers. I know a few people who phrase comments this way, and often they're just translating literally from their native language.
>The entitlement from some of the people in that thread is insane.
That is not a display of entitlement at all.
Users complaining about changes in a product that they do not like is a good thing and must be encouraged. If nobody says anything and just "takes it" things will stay the same. How much weight you want to give to those comments can be argued. Certainly much like in the case of restaurant reviews, a vocal minority can be negative, but you can take them with a grain of salt.
When I worked on bugs I would always be careful to note that kind of reason even if I was a little too terse for the users.. I'd hate to see the motivated new hire try to improve ease of use by examining closed bugs like this one.
For example, open a new default tab--the one with a google search bar. Fullscreen it. Now try to enter a search. I get a "Please enter a URL" popup and the page is unusable. I maintain that "This default thing on your screen should not work and gives you an impossible instruction" is a weird design decision. https://code.google.com/p/chromium/issues/detail?id=533935
A real report would have said something like "No way to enter a url on fullscreen tab". That might have survived 'bug triage'.
My Goodness, I learnt a new trick from you!!
Also the project is a Google project and isn't it the Dev responsibility to read, consider the features and bugs, yes users will always want more, but honestly they should sit back and think about this feature, I say that they all use Mac OS and in Mac OS you can enter URL on full screen tab :D
Anyways I shifted to firefox, also the dev who said "this is as per design", it is a huge irony that they work in the same org who made such a beautiful material design, I only wonder how Android would have looked had they taken such a careless approach regarding its "design"
apparently everything third party says is as per design and won't change, even if it is significant improvement and this feature makes sense and 500+ people have raised the same request, of course you don't listen to everyone but 500 people took time to upvote it so it is worth a look from the dev side also if all FOSS projects are going to be run like this then God help us.
Are you serious?
Try using firefox in full screen mode and chrome in full screen mode on win or linux and you'll understand, and as far as dictating app behavior is concerned that is the whole point of open source right? If they think we all are trash then why open source it? just for namesake?
Same feature is available in FF and IE since centuries, apparently the designers of FF and IE were idiots then
Unmoderated bugtrackers for open source projects only worked when the people who knew about them were a self selecting group. It's becoming clear that a new model is going to be needed.