IE users cannot use inline-pickers or find html forms to change their data

Bug #954072 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Curtis Hovey

Bug Description

The inline picker code used to render dynamic widgets in the page has this amateur fragment of code in the script block:

    if (Y.UA.ie) {
        return;
    }

The code supports script and no-script situations, but the script will not execute for IE users. The link to the html form is never rendered for the user. The inline-picker was retrofitted to many pages. The blueprint page uses them exclusively...meaning that the page excludes IE users. Pages such as the project page were updated to use the inline-picker because it provides better warnings and workflows to fix unsecure situations that all users really should see; turning off JS is also a choice to opt out of help, but IE users re not given a choice.

Why is this? What does ALL versions of IE not support? Why is there a noscript block...why not use plain HTML and add features to it when the browser supports the feature?

Related branches

Revision history for this message
William Grant (wgrant) wrote :

I have a branch which removes the anti-IE guard, but we should also have a non-AJAX fallback.

Curtis Hovey (sinzui)
Changed in launchpad:
assignee: nobody → Curtis Hovey (sinzui)
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
tags: added: disclosure sharing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.