Last modified: 2013-06-05 17:02:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T51140, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 49140 - IE9, beta labs (at least): Feedback interface appears then disappears
IE9, beta labs (at least): Feedback interface appears then disappears
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
ArticleFeedbackv5 (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: browser-test-bug
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-04 16:49 UTC by Chris McMahon
Modified: 2013-06-05 17:02 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris McMahon 2013-06-04 16:49:00 UTC
Seen in IE9 on beta labs: 

AFTv5 is enabled on all pages in beta enwiki, but see for example http://en.wikipedia.beta.wmflabs.org/wiki/Aftpage. 

In IE9 (at least), the "Help improve this page" interface appears briefly and then disappears.  

Not seen in Chrome/FF. (Not yet checked in earlier versions of IE)
Comment 1 Andre Klapper 2013-06-04 17:48:02 UTC
Cannot reproduce using IE 8.0.6001.18702 on Windows XP Professional SP3 on http://en.wikipedia.beta.wmflabs.org/wiki/Aftpage . I tried both not being logged in and being logged in.
Comment 2 Matthias Mullie 2013-06-05 09:47:47 UTC
I think I just had this happen once, but since I refreshed, everything seems fine. Chris: does it still occur for you?
Comment 3 Chris McMahon 2013-06-05 17:02:16 UTC
We had not explicitly clicked "Enable feedback" for the page in question in beta labs. 

The flickering AFT input on random pages where feedback is not enabled is likely a cache artifact, it seems unlikely that we would see that in production, and if we do it would be a separate issue from this.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links