-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 2.0+
SInce the introduction of the revamped "new Item" page the list of items that can be populated via an XMLHttpRequest.
However this is a bad thing to do as the list should not be considered static.
OSS can add to the list if a plugin is installed.
Third party extensions can contribute items (and even remove items from the list) dynamically.
This causes a big issue with IE as by default IE legitimatley caches the responses of an XMLHttpRequest unless told otherwise.
Workaround is to force a reload after cleaning the cache - but this is bad UX.
NOTE: there are probably other places in jenkins core that handle XMLHttpRequest requests that are not adding correct cache control headers - this should probably be investigated too.
Found with IE 11 on windows 10 but likely affects all versions of IE 11 and possibly (but untested Edge)
Steps to reproduce:
- Load the New Item page in your IE11 browser
- Install a new plugin which provides a new Item type
- Navigate to the new Item page again in your browser
Observed Behavior:
- You will not see the new item listed
Expected Behavior:
- The new item should show up in the list without a special action or refresh by the user
[JENKINS-43848] new item categories served without cache expiration
Description |
Original:
SInce the introduction of the revamped "new Item" page the list of items that can be populated via an {{XMLHttpRequest}}. However this is a bad thing to do as the list should not be considered static. OSS can add to the list if a plugin is installed. Third party extensions can contribute items (and even remove items from the list) dynamically. This causes a big issue with IE as by default IE legitimatley caches the responses of an {{XMLHttpRequest}} unless told otherwise. Workaround is to force a reload after cleaning the cache - but this is bad UX. NOTE: there are probably other places in jenkins core that handle {{XMLHttpRequest}} requests that are not adding correct cache control headers - this should probably be investigated too. |
New:
SInce the introduction of the revamped "new Item" page the list of items that can be populated via an {{XMLHttpRequest}}. However this is a bad thing to do as the list should not be considered static. OSS can add to the list if a plugin is installed. Third party extensions can contribute items (and even remove items from the list) dynamically. This causes a big issue with IE as by default IE legitimatley caches the responses of an {{XMLHttpRequest}} unless told otherwise. Workaround is to force a reload after cleaning the cache - but this is bad UX. NOTE: there are probably other places in jenkins core that handle {{XMLHttpRequest}} requests that are not adding correct cache control headers - this should probably be investigated too. Found with IE 11 on windows 10 but likely affects all versions of IE 11 and possibly (but untested Edge) |
Labels | New: UX http regression |
Environment | New: Jenkins 2.0+ |
Assignee | New: Manuel Recena Soto [ recena ] |
Labels | Original: UX http regression | New: regression |
Description |
Original:
SInce the introduction of the revamped "new Item" page the list of items that can be populated via an {{XMLHttpRequest}}. However this is a bad thing to do as the list should not be considered static. OSS can add to the list if a plugin is installed. Third party extensions can contribute items (and even remove items from the list) dynamically. This causes a big issue with IE as by default IE legitimatley caches the responses of an {{XMLHttpRequest}} unless told otherwise. Workaround is to force a reload after cleaning the cache - but this is bad UX. NOTE: there are probably other places in jenkins core that handle {{XMLHttpRequest}} requests that are not adding correct cache control headers - this should probably be investigated too. Found with IE 11 on windows 10 but likely affects all versions of IE 11 and possibly (but untested Edge) |
New:
SInce the introduction of the revamped "new Item" page the list of items that can be populated via an {{XMLHttpRequest}}. However this is a bad thing to do as the list should not be considered static. OSS can add to the list if a plugin is installed. Third party extensions can contribute items (and even remove items from the list) dynamically. This causes a big issue with IE as by default IE legitimatley caches the responses of an {{XMLHttpRequest}} unless told otherwise. Workaround is to force a reload after cleaning the cache - but this is bad UX. NOTE: there are probably other places in jenkins core that handle {{XMLHttpRequest}} requests that are not adding correct cache control headers - this should probably be investigated too. Found with IE 11 on windows 10 but likely affects all versions of IE 11 and possibly (but untested Edge) Steps to reproduce: * Load the New Item page in your IE11 browser * Install a new plugin which provides a new Item type * Navigate to the new Item page again in your browser * Observed Behavior: * You will not see the new item listed Expected Behavior: * The new item should show up in the list without a special action or refresh by the user |
Assignee | Original: Manuel Recena Soto [ recena ] | New: Josiah Haswell [ jhaswell ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "jenkins#2973 (Web Link)" [ 17433 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |