Opened 18 years ago
Closed 17 years ago
#7367 closed defect (bug) (fixed)
Redundant logic in script and style queuing classes
| Reported by: | sambauers | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Optimization | Version: | 2.6 |
| Severity: | minor | Keywords: | dev-feedback |
| Cc: | Focuses: |
Description
I am pretty sure that the changes here:
http://trac.wordpress.org/changeset/8301/trunk/wp-includes/class.wp-scripts.php
And here:
http://trac.wordpress.org/changeset/8301/trunk/wp-includes/class.wp-styles.php
Introduce redundant code.
WP_CONTENT_URL should always be a fully qualified URL so it will match the first condition and never reach the second.
I think these should be reverted, but maybe I'm just not reading it right.
Change History (8)
#2
@
18 years ago
- Milestone 2.6.1 → 2.7
Moving to 2.7, since it will have to be added to trunk first.
#6
@
18 years ago
- Keywords BackPress added
- Milestone → 2.8
- Resolution invalid
- Status closed → reopened
- Summary Maybe redundant logic in script and style queuing classes → Redundant logic in script and style queuing classes
If the logic is followed in all cases except misconfiguration this additional part of the condition is definately redundant. It also diverges from the original abstract BackPress class by imtroducing a WordPress specific constant.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
It appears that if the $src is relative, it will try to add on the WP_CONTENT_URL to the $src to ensure that the relative link is pointing to the right location.
I don't believe it is about WP_CONTENT_URL and about the location of the CSS or Script file.