[wp-trac] Re: [WordPress Trac] #8181: css-related bug found in
media.php
WordPress Trac
wp-trac at lists.automattic.com
Mon Jan 26 20:01:38 GMT 2009
#8181: css-related bug found in media.php
-------------------------------------+--------------------------------------
Reporter: LHLDevAdmin | Owner: anonymous
Type: enhancement | Status: new
Priority: normal | Milestone: 2.8
Component: Optimization | Version: 2.6.1
Severity: minor | Resolution:
Keywords: needs-patch 2nd-opinion |
-------------------------------------+--------------------------------------
Comment (by LHLDevAdmin):
Replying to [comment:5 mrmist]:
> Is this not done by design? I mean yes it does seem syntactically
broken, but isn't that inline style stuff only pushed if a plugin has
specifically overriden it?
>
> I guess it could all be punted to a dynamically-generaed stylesheet,
though that might be really complicated to achieve.
I'm not sure whether I'm reading sarcasm or frustration, so I'll assume
the latter.
I'm not sure of the technical definition of 'plugin,' by which you
operate, but one would think the image gallery option within WordPress is
part of the software. Therefore, one should not present 3rd-party plugin
excuses as arguments against doing something correctly. If I wanted
software that selectively adheres to web-compliance standards, then I'd
buy a Microsoft product.
Undoubtedly, a dynamically-generated style sheet would be complicated to
achieve, and I'm not suggesting you try it. However, examples abound
where master and theme-based style sheets working together successfully
within the application. In those examples (MS SharePoint comes to mind),
the master style sheet is not dynamically generated; rather, they are
deployed with the software and re-deployed with each software version
update.
With a master style sheet, which sets above the themes sub-directory
within the site structure, you could include all styles associated with
your plugin (meaning those deployed with the software). This style sheet,
like all other software-related files within WordPress, can be overwritten
with each version update.
As long as WordPress uses class tags to call the styles, I can (where
needed) write code (at the theme level) to override the master styles.
Under the current deployment scenario, I'm forced either (a) to accept
sloppy coding or (b) to modify the software after every WordPress update.
--
Ticket URL: <http://trac.wordpress.org/ticket/8181#comment:6>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list