#24495 closed defect (bug) (invalid)
thickbox's inline content will not trigger unless it is preceeded by an ampersand
| Reported by: | Clorith | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | External Libraries | Version: | 3.5.1 |
| Severity: | minor | Keywords: | |
| Cc: | Focuses: |
Description
When using the built in thickbox, you are required to set up your links with an ampersand before the inlineId parameter or it will not pick this up.
This means that by calling inline content with <a href="#TB_inline?inlineID=foo-bar">, you will get an empty thickbox, where as calling <a href="#TB_inline?&inlineID=foo-bar"> it will function as intended and load the inline content for the thickbox.
Change History (4)
#2
@
13 years ago
- Resolution wontfix
- Status closed → reopened
Thickbox is still used for plugin and theme information in list tables.
#3
@
13 years ago
Thickbox is also the modal manager referenced in the Codex so I wouldn't be surprised if existing and potential future plugins are and will be trying to use it so long as it remains in core and no new alternative is made available to them.
Not sure if it's referenced in the upcoming handbooks or not but as it stands the Codex is still the go-to place for developer information.
#4
@
12 years ago
- Milestone Awaiting Review
- Resolution → invalid
- Status reopened → closed
I cannot reproduce this with current core Thickbox files: http://jsfiddle.net/AfAL6/1/
Note that it seems to be necessary to have another wrapping HTML element (like a <p>) in the element which has the desired inlineID.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Since thickbox was abandoned and it's usage replaced with the new media model, core shouldn't maintain it beyond any security issues that may come up.