[development] What does IE8 mean for Drupal?

[Victor Kane]

This is an interesting point.

One would think, that in the scheme of clean separation between
presentation and business logic (code) layers, the choice of quirk
mode would fit into the presentation layer.

But I feel this is more than a presentation question, the decision to
go XHTML/CSS standards compliant crosses the gray line into an
architectural decision for a given site or web application. That's why
I don't see it as a purely presentation design issue.

And what about sites that have optional themes, or are multi-themes?

Of course, I think the theme should be able to override too.

On a practical level, the decision would be made in an early iteration
of the development cycle, to go standards compliant, and then there
might be a whole succession of themes or even parrallel theme
development. I would want to avoid obligatory redundancy there.

That's what I was thinking.

Victor Kane
http://

On Jan 25, 2008 8:31 PM, Laura Scott <laura at pingv.com> wrote:
> On Jan 25, 2008, at 5:19 AM, Victor Kane wrote:
>
> > Again, whatever is adopted, all that Drupal needs to do is make the
> > switch accessible via admin interface (I would be strongly against
> > leaving this to a theme level, since it is a royal PITA to have to
> > redo settings while changing themes).
>
> I feel just the opposite. This is totally a theming issue, and how
> it's addressed would depend upon the theme approach altogether.
>
> Also, another dissenting view on this whol special-tag thing: http://
> realtech.burningbird.net/standards/bobbing-heads-and-the-ie8-meta-tag/
>
> Laura
>