3 ms·

Hmm.. I dunno. It seems pretty preposterous to decline a bug with no comment whatsoever and then to have 33 more people confirm the bug after it being declined.

by awolf 15y ago

Hmm.. I dunno. It seems pretty preposterous to decline a bug with no comment whatsoever and then to have 33 more people confirm the bug after it being declined. This thing is 3 years old now. If "doesn't give a fuck" doesn't describe google's stance on this, how would you describe it?

clownz0r 15y ago
"Simple workaround exists" maybe? I'm not saying this bug isn't a problem (especially for developers new to Android), just trying to guess what they might have been thinking when they declined it. People still reporting the problem 3 years later should be a pretty good indicator that this bug needs to be fixed though.