"Post your feedback" greyed out in ArticleFeedbackv5
Closed, ResolvedPublic

Description

Author: asheesh

Description:
Screenshot (with DOM) of partly-greyed-out button

To reproduce the bug I found:

  1. Open a new browser session. Make sure you're *not* logged in to Wikipedia.
  1. Leave a piece of feedback on http://en.wikipedia.org/wiki/Drew_Barrymore?aftv5_form=1&aftv5_link=E
  1. Log in to Wikipedia
  1. Visit http://en.wikipedia.org/wiki/Drew_Barrymore?aftv5_form=1&aftv5_link=E and notice that the "Post your feedback" looks pale and "greyed out", even after I type in a message and click "Yes"/"No", but in fact the button still works properly

I can reproduce this with Iceweasel on Debian sid (Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20100101 Firefox/10.0.4 Iceweasel/10.0.4) and Chromium on Debian sid (Chromium 18.0.1025.168 (Developer Build 134367) Debian wheezy/sid).

Attaching screenshots.


Version: unspecified
Severity: major

Attached:

Details

bzimport set Reference to bz37431.
bzimport added a subscriber: Unknown Object (MLST).
bzimport created this task.Jun 9 2012, 6:28 PM

asheesh wrote:

Similar screenshot with Adblock plus disabled

Lest you think Adblock is to blame, this screenshot reproduces the behavior with AdBlock Plus disabled. (-:

Attached:

articles wrote:

We also have this installed on a development site right now, and that is also our problem is the submit button is greyed out and does not work. Any insights would be good. We have mediawiki 1.19 and using the articles feedback version 5.

Asheesh: Not sure where it's only *partly* greyed out - could you elaborate?

You wrote that it also happens in Chromium, but you could check if the problem still happen if you start Iceweasel/Firefox in Safe Mode? (Safe Mode disables extensions and themes, hardware acceleration and some JavaScript stuff in order to exclude some possible reasons for problems. It does not disable plugins which are add-ons.) See http://support.mozilla.com/en-US/kb/Safe+Mode

  • This bug has been marked as a duplicate of bug 41653 ***

Add Comment