By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,723 Members | 1,655 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,723 IT Pros & Developers. It's quick & easy.

Improvement of attribute "style"

P: n/a
How much are you interested that the attribute "style" will offer the
same or similar capabilities like they are provided by the element
"style" in the element "head"?

Do you want that the document "Syntax of CSS rules in HTML's "style"
attribute" (http://www.w3.org/TR/css-style-attr) will become an
official recommendation in the near future?

Best regards,
Markus Elfring
Jul 20 '05 #1
Share this Question
Share on Google+
52 Replies


P: n/a
On Thu, 15 Apr 2004, Markus Elfring wrote:
How much are you interested that the attribute "style" will offer the
same or similar capabilities like they are provided by the element
"style" in the element "head"?


Not much. Ideally there should be no attribute "style" in HTML. It
tempts authors to just repeat the nonsenses of HTML/3.2, just in a
more-verbose language.

Jul 20 '05 #2

P: n/a
Ma************@web.de (Markus Elfring) wrote:
How much are you interested that the attribute "style" will offer the
same or similar capabilities like they are provided by the element
"style" in the element "head"?
Not much. In the interests of clean code I try to use external styles
wherever possible. Use of the style attribute should, IMO, be rare.
Do you want that the document "Syntax of CSS rules in HTML's "style"
attribute" (http://www.w3.org/TR/css-style-attr) will become an
official recommendation in the near future?


I can see some problems with backwards compatability.
To take their second example:
<p style="{color: #090; line-height: 1.2}
::first-letter {color: #900}">...</p>
One would hope that a CSS1 or CSS2 compliant browser would apply the
color and line-height properties and ignore the CSS3 ::first-letter
syntax. However the syntax proposed here with the inclusion of {}
means that older (in other words current) browsers ignore all the
styles. Not ideal.

That document is nearly two years old, has any further work been done
on this? Or are you just trying to raise the dead?

Steve

--
"My theories appal you, my heresies outrage you,
I never answer letters and you don't like my tie." - The Doctor

Steve Pugh <st***@pugh.net> <http://steve.pugh.net/>
Jul 20 '05 #3

P: n/a
On Thu, 15 Apr 2004, Markus Elfring wrote:
How much are you interested that the attribute "style" will offer the
same or similar capabilities like they are provided by the element
"style" in the element "head"?


Not much. Ideally there should be no attribute "style" in HTML. It
tempts authors to just repeat the nonsenses of HTML/3.2, just in a
more-verbose language.

Jul 20 '05 #4

P: n/a
Markus Elfring wrote:
How much are you interested that the attribute "style" will offer the
same or similar capabilities like they are provided by the element
"style" in the element "head"?

Do you want that the document "Syntax of CSS rules in HTML's "style"
attribute" (http://www.w3.org/TR/css-style-attr) will become an
official recommendation in the near future?

Best regards,
Markus Elfring


Not at all. I prefer to put style in a separate file and link to it,
the only exception being when I'm providing a single-file example to
someone, in which case I put all of the style info inside the <head>.

Chris Beall

Jul 20 '05 #5

P: n/a
Markus Elfring wrote:
How much are you interested that the attribute "style" will offer the
same or similar capabilities like they are provided by the element
"style" in the element "head"?

Do you want that the document "Syntax of CSS rules in HTML's "style"
attribute" (http://www.w3.org/TR/css-style-attr) will become an
official recommendation in the near future?

Best regards,
Markus Elfring


Not at all. I prefer to put style in a separate file and link to it,
the only exception being when I'm providing a single-file example to
someone, in which case I put all of the style info inside the <head>.

Chris Beall

Jul 20 '05 #6

P: n/a
"Markus Elfring" <Ma************@web.de> wrote in
comp.infosystems.www.authoring.stylesheets:
How much are you interested that the attribute "style" will offer the
same or similar capabilities like they are provided by the element
"style" in the element "head"?


I'm not at all interested in such an extension.

I use the style="..." attribute now, when I'm too lazy to update my
style sheet. I nearly always regret it as I end up having the same
style attribute repeated multiple times in the document (or multiple
documents). Then I have more work to update the style sheet and
change all the documents to what they should have been in the first
place.

Why create additional capabilities that solve no real problem and
will only encourage misuse?

--
Stan Brown, Oak Road Systems, Cortland County, New York, USA
http://OakRoadSystems.com/
HTML 4.01 spec: http://www.w3.org/TR/html401/
validator: http://validator.w3.org/
CSS 2 spec: http://www.w3.org/TR/REC-CSS2/
2.1 changes: http://www.w3.org/TR/CSS21/changes.html
validator: http://jigsaw.w3.org/css-validator/
Jul 20 '05 #7

P: n/a
"Markus Elfring" <Ma************@web.de> wrote in
comp.infosystems.www.authoring.stylesheets:
How much are you interested that the attribute "style" will offer the
same or similar capabilities like they are provided by the element
"style" in the element "head"?


I'm not at all interested in such an extension.

I use the style="..." attribute now, when I'm too lazy to update my
style sheet. I nearly always regret it as I end up having the same
style attribute repeated multiple times in the document (or multiple
documents). Then I have more work to update the style sheet and
change all the documents to what they should have been in the first
place.

Why create additional capabilities that solve no real problem and
will only encourage misuse?

--
Stan Brown, Oak Road Systems, Cortland County, New York, USA
http://OakRoadSystems.com/
HTML 4.01 spec: http://www.w3.org/TR/html401/
validator: http://validator.w3.org/
CSS 2 spec: http://www.w3.org/TR/REC-CSS2/
2.1 changes: http://www.w3.org/TR/CSS21/changes.html
validator: http://jigsaw.w3.org/css-validator/
Jul 20 '05 #8

P: n/a
> ... I nearly always regret it as I end up having the same
style attribute repeated multiple times in the document (or multiple
documents). Then I have more work to update the style sheet and
change all the documents to what they should have been in the first
place.
Would you like to try the forth use case "Importing a style sheet to
apply as a scoped style sheet"?
http://www.w3.org/TR/css-style-attr#examples

Why create additional capabilities that solve no real problem and
will only encourage misuse?


What do think is the "head" part for a portal component?
http://en.wikipedia.org/wiki/Portlet

Where can the specific formatting be placed for it?

Kind regards,
Markus Elfring
Jul 20 '05 #9

P: n/a
> ... I nearly always regret it as I end up having the same
style attribute repeated multiple times in the document (or multiple
documents). Then I have more work to update the style sheet and
change all the documents to what they should have been in the first
place.
Would you like to try the forth use case "Importing a style sheet to
apply as a scoped style sheet"?
http://www.w3.org/TR/css-style-attr#examples

Why create additional capabilities that solve no real problem and
will only encourage misuse?


What do think is the "head" part for a portal component?
http://en.wikipedia.org/wiki/Portlet

Where can the specific formatting be placed for it?

Kind regards,
Markus Elfring
Jul 20 '05 #10

P: n/a
Markus Elfring wrote:
What do think is the "head" part for a portal component?
http://en.wikipedia.org/wiki/Portlet

Where can the specific formatting be placed for it?


You apply a class to the included HTML and then use a descendent selector in
the external CSS.

--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Jul 20 '05 #11

P: n/a
Markus Elfring wrote:
What do think is the "head" part for a portal component?
http://en.wikipedia.org/wiki/Portlet

Where can the specific formatting be placed for it?


You apply a class to the included HTML and then use a descendent selector in
the external CSS.

--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Jul 20 '05 #12

P: n/a
> You apply a class to the included HTML and then use a descendent selector in
the external CSS.


What should happen if a portlet would like to style itself independent
from central style specifications in the HTML head?
It might include or import a private style sheet for that purpose.
Jul 20 '05 #13

P: n/a
> You apply a class to the included HTML and then use a descendent selector in
the external CSS.


What should happen if a portlet would like to style itself independent
from central style specifications in the HTML head?
It might include or import a private style sheet for that purpose.
Jul 20 '05 #14

P: n/a
Markus Elfring wrote:
You apply a class to the included HTML and then use a descendent selector
in the external CSS.


What should happen if a portlet would like to style itself independent
from central style specifications in the HTML head?


Then it should remember that its part of a larger page.

--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Jul 20 '05 #15

P: n/a
Markus Elfring wrote:
You apply a class to the included HTML and then use a descendent selector
in the external CSS.


What should happen if a portlet would like to style itself independent
from central style specifications in the HTML head?


Then it should remember that its part of a larger page.

--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Jul 20 '05 #16

P: n/a
David Dorward wrote:
Markus Elfring wrote:
You apply a class to the included HTML and then use a descendent
selector in the external CSS.


What should happen if a portlet would like to style itself
independent from central style specifications in the HTML head?


Then it should remember that its part of a larger page.


While I agree with the proponents of avoiding the "style" attribute, Markus
makes 0one good point with portlets here.

The idea of portlets is distribution of same content to various
environments, and the controller of a portlet's appearance is its provider,
not the user. For example, if a weather service offers a free portlet with
forecast for a town, they might want it to have a predefined look.

However, I am still against using a bunch of "style" attributes in a
portlet. Maybe some kind of specifying an external CSS file just for that
portion, or simply to use iframe or even Flash.

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.
Jul 20 '05 #17

P: n/a
David Dorward wrote:
Markus Elfring wrote:
You apply a class to the included HTML and then use a descendent
selector in the external CSS.


What should happen if a portlet would like to style itself
independent from central style specifications in the HTML head?


Then it should remember that its part of a larger page.


While I agree with the proponents of avoiding the "style" attribute, Markus
makes 0one good point with portlets here.

The idea of portlets is distribution of same content to various
environments, and the controller of a portlet's appearance is its provider,
not the user. For example, if a weather service offers a free portlet with
forecast for a town, they might want it to have a predefined look.

However, I am still against using a bunch of "style" attributes in a
portlet. Maybe some kind of specifying an external CSS file just for that
portion, or simply to use iframe or even Flash.

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.
Jul 20 '05 #18

P: n/a
> Then it should remember that its part of a larger page.

A portlet has got a reference to its context to access global
informations. But I want that it should keep specific syles in its own
section.
A portlet may need its own CSS rules.
Jul 20 '05 #19

P: n/a
> Then it should remember that its part of a larger page.

A portlet has got a reference to its context to access global
informations. But I want that it should keep specific syles in its own
section.
A portlet may need its own CSS rules.
Jul 20 '05 #20

P: n/a
"Berislav Lopac" <be************@dimedia.hr> wrote:
While I agree with the proponents of avoiding the "style" attribute, Markus
makes 0one good point with portlets here.
I've been reading this thread the last few days and wondering WTF a "portlet" is?

The idea of portlets is distribution of same content to various
environments, and the controller of a portlet's appearance is its provider,
not the user.
Ah, so it's just a euphemism for advertisement. Who would have guessed?

For example, if a weather service offers a free portlet with
forecast for a town, they might want it to have a predefined look.
Why? Oh yeah, because it ain't "free", it's advertising.

However, I am still against using a bunch of "style" attributes in a
portlet. Maybe some kind of specifying an external CSS file just for that
portion, or simply to use iframe or even Flash.


Good idea. Let them go to iframe oblivion where adverts belong.

--
iframe { display: none !important; /* Goodbye doubleclick */}
Jul 20 '05 #21

P: n/a
"Berislav Lopac" <be************@dimedia.hr> wrote:
While I agree with the proponents of avoiding the "style" attribute, Markus
makes 0one good point with portlets here.
I've been reading this thread the last few days and wondering WTF a "portlet" is?

The idea of portlets is distribution of same content to various
environments, and the controller of a portlet's appearance is its provider,
not the user.
Ah, so it's just a euphemism for advertisement. Who would have guessed?

For example, if a weather service offers a free portlet with
forecast for a town, they might want it to have a predefined look.
Why? Oh yeah, because it ain't "free", it's advertising.

However, I am still against using a bunch of "style" attributes in a
portlet. Maybe some kind of specifying an external CSS file just for that
portion, or simply to use iframe or even Flash.


Good idea. Let them go to iframe oblivion where adverts belong.

--
iframe { display: none !important; /* Goodbye doubleclick */}
Jul 20 '05 #22

P: n/a
> I've been reading this thread the last few days and wondering WTF a "portlet" is?

I suggest to read the article "http://en.wikipedia.org/wiki/Portlet".

Please consider also these standards.
- Web Services for Remote Portlets
http://oasis-open.org/committees/tc_...wg_abbrev=wsrp
http://webcollage.com/html/products/..._wsia_wsrp.pdf

- Web Services for Interactive Applications
http://oasis-open.org/committees/tc_...wg_abbrev=wsia
http://oasis-open.org/committees/wsi...os/index.shtml

Would you like to develop new web experiences with it?

Ah, so it's just a euphemism for advertisement. Who would have guessed?
Companies can publish advertisements with portlet technologies. But
this discussion is not about advertisement purpose.

Why? Oh yeah, because it ain't "free", it's advertising.
How do you think about to look at portlet catalogs for providers?
- https://www-306.ibm.com/services/cwi/portal/_pagr/105/
- http://portlet-opensrc.sourceforge.net/

Good idea. Let them go to iframe oblivion where adverts belong.


A portlet can be free to provide content with related style by all
techniques that are appropriate for its service.
Jul 20 '05 #23

P: n/a
> I've been reading this thread the last few days and wondering WTF a "portlet" is?

I suggest to read the article "http://en.wikipedia.org/wiki/Portlet".

Please consider also these standards.
- Web Services for Remote Portlets
http://oasis-open.org/committees/tc_...wg_abbrev=wsrp
http://webcollage.com/html/products/..._wsia_wsrp.pdf

- Web Services for Interactive Applications
http://oasis-open.org/committees/tc_...wg_abbrev=wsia
http://oasis-open.org/committees/wsi...os/index.shtml

Would you like to develop new web experiences with it?

Ah, so it's just a euphemism for advertisement. Who would have guessed?
Companies can publish advertisements with portlet technologies. But
this discussion is not about advertisement purpose.

Why? Oh yeah, because it ain't "free", it's advertising.
How do you think about to look at portlet catalogs for providers?
- https://www-306.ibm.com/services/cwi/portal/_pagr/105/
- http://portlet-opensrc.sourceforge.net/

Good idea. Let them go to iframe oblivion where adverts belong.


A portlet can be free to provide content with related style by all
techniques that are appropriate for its service.
Jul 20 '05 #24

P: n/a
Karl Smith wrote:
"Berislav Lopac" <be************@dimedia.hr> wrote:
The idea of portlets is distribution of same content to various
environments, and the controller of a portlet's appearance is its
provider, not the user.


Ah, so it's just a euphemism for advertisement. Who would have
guessed?

For example, if a weather service offers a free portlet with
forecast for a town, they might want it to have a predefined look.


Why? Oh yeah, because it ain't "free", it's advertising.


Portlets are not advertising. They are regular content.

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.
Jul 20 '05 #25

P: n/a
Karl Smith wrote:
"Berislav Lopac" <be************@dimedia.hr> wrote:
The idea of portlets is distribution of same content to various
environments, and the controller of a portlet's appearance is its
provider, not the user.


Ah, so it's just a euphemism for advertisement. Who would have
guessed?

For example, if a weather service offers a free portlet with
forecast for a town, they might want it to have a predefined look.


Why? Oh yeah, because it ain't "free", it's advertising.


Portlets are not advertising. They are regular content.

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.
Jul 20 '05 #26

P: n/a
Stan Brown wrote:
[snip]
I'm not at all interested in such an extension.

I use the style="..." attribute now, when I'm too lazy to update my
style sheet. I nearly always regret it as I end up having the same
style attribute repeated multiple times in the document (or multiple
documents). Then I have more work to update the style sheet and
change all the documents to what they should have been in the first
place.

[snip]

How would you, or others here, solve this problem?

I am writing a page based on a template that has a CSS. Lots of pages use that
CSS. This page needs some rules that are local to this page, because of the
special nature of its content, and I don't expect them to used elsewhere.

After some thought, I have given this page its own CSS, which then uses
@import for the standard CSS for this template. As far as I can tell, this
works OK, although I believe this will not work properly in NN4, and will hide
the standard CSS.

But I did contemplate using embedded or inline styles. (Probably the thing
that stopped me was that I never used them before, and I didn't want to start
now).

Views? (I'm not sure how like the "portlet" case this is).

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #27

P: n/a
Stan Brown wrote:
[snip]
I'm not at all interested in such an extension.

I use the style="..." attribute now, when I'm too lazy to update my
style sheet. I nearly always regret it as I end up having the same
style attribute repeated multiple times in the document (or multiple
documents). Then I have more work to update the style sheet and
change all the documents to what they should have been in the first
place.

[snip]

How would you, or others here, solve this problem?

I am writing a page based on a template that has a CSS. Lots of pages use that
CSS. This page needs some rules that are local to this page, because of the
special nature of its content, and I don't expect them to used elsewhere.

After some thought, I have given this page its own CSS, which then uses
@import for the standard CSS for this template. As far as I can tell, this
works OK, although I believe this will not work properly in NN4, and will hide
the standard CSS.

But I did contemplate using embedded or inline styles. (Probably the thing
that stopped me was that I never used them before, and I didn't want to start
now).

Views? (I'm not sure how like the "portlet" case this is).

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #28

P: n/a
Barry Pearson wrote:
[snip]
After some thought, I have given this page its own CSS, which then
uses @import for the standard CSS for this template. As far as I can
tell, this works OK, although I believe this will not work properly
in NN4, and will hide the standard CSS.

[snip]

ps: If simply linking to the 2 CSSs from the HTML works reliably, then that
would be a better option. It appears to be OK on the W2000 browsers I test
with.

But I haven't got a Mac, and I'm used to things I do failing with IE Mac then
only finding out later. And I also have no idea about how well it works in
other systems.

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #29

P: n/a
Barry Pearson wrote:
[snip]
After some thought, I have given this page its own CSS, which then
uses @import for the standard CSS for this template. As far as I can
tell, this works OK, although I believe this will not work properly
in NN4, and will hide the standard CSS.

[snip]

ps: If simply linking to the 2 CSSs from the HTML works reliably, then that
would be a better option. It appears to be OK on the W2000 browsers I test
with.

But I haven't got a Mac, and I'm used to things I do failing with IE Mac then
only finding out later. And I also have no idea about how well it works in
other systems.

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #30

P: n/a
> The idea of portlets is distribution of same content to various
environments, and the controller of a portlet's appearance is its provider,
not the user. For example, if a weather service offers a free portlet with
forecast for a town, they might want it to have a predefined look.
Are portlet providers interested to use complete CSS rules?
Are rules for merging the appearance guidelines with styles from a
portal needed?

However, I am still against using a bunch of "style" attributes in a
portlet. Maybe some kind of specifying an external CSS file just for that
portion, or simply to use iframe or even Flash.


There are problems with the support for inline frame windows.
http://www.cs.tut.fi/~jkorpela/html/iframe.html

If you want an external CSS file, I assume that you would like to see
further development and support of the discussed specification.
Jul 20 '05 #31

P: n/a
> The idea of portlets is distribution of same content to various
environments, and the controller of a portlet's appearance is its provider,
not the user. For example, if a weather service offers a free portlet with
forecast for a town, they might want it to have a predefined look.
Are portlet providers interested to use complete CSS rules?
Are rules for merging the appearance guidelines with styles from a
portal needed?

However, I am still against using a bunch of "style" attributes in a
portlet. Maybe some kind of specifying an external CSS file just for that
portion, or simply to use iframe or even Flash.


There are problems with the support for inline frame windows.
http://www.cs.tut.fi/~jkorpela/html/iframe.html

If you want an external CSS file, I assume that you would like to see
further development and support of the discussed specification.
Jul 20 '05 #32

P: n/a
*Berislav Lopac* <be************@dimedia.hr>:

Portlets are not advertising. They are regular content.


They're imported content advertising their provider.

--
I'm a signature virus, help me spread!
Jul 20 '05 #33

P: n/a
*Berislav Lopac* <be************@dimedia.hr>:

Portlets are not advertising. They are regular content.


They're imported content advertising their provider.

--
I'm a signature virus, help me spread!
Jul 20 '05 #34

P: n/a
> If simply linking to the 2 CSSs from the HTML works reliably, then that
would be a better option.


Where do you want to place your CSS code now?
Have you got the need to put some special formatting rules into the
style attribute somewhere in the body part?
Jul 20 '05 #35

P: n/a
> If simply linking to the 2 CSSs from the HTML works reliably, then that
would be a better option.


Where do you want to place your CSS code now?
Have you got the need to put some special formatting rules into the
style attribute somewhere in the body part?
Jul 20 '05 #36

P: n/a
Markus Elfring wrote:
If simply linking to the 2 CSSs from the HTML works reliably, then
that would be a better option.


Where do you want to place your CSS code now?
Have you got the need to put some special formatting rules into the
style attribute somewhere in the body part?


Up to now, every page I have has one link to a CSS file. And those CSSs
(obviously I have a number of them) are the only place where I have any
styles.

Now I am writing a page that needs a few extra rules, almost certainly
one-off, and I don't want them in the normal CSS for that page layout. I'm
confident that the @import approach will work in most cases, but I believe
fails in NN4. A more logical approach would be to link to 2 CSSs from that
page, and as far as I can tell it is OK in my test set of browsers on W2000,
but I can't test on other platforms.

Using a style attribute would be another option. I have avoided styles within
my HTML pages so far, and would prefer to keep things that way. So I am trying
to find the best cross-browser, least-unsatisfactory, way of adding a few
specialist styles for that page.

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #37

P: n/a
Markus Elfring wrote:
If simply linking to the 2 CSSs from the HTML works reliably, then
that would be a better option.


Where do you want to place your CSS code now?
Have you got the need to put some special formatting rules into the
style attribute somewhere in the body part?


Up to now, every page I have has one link to a CSS file. And those CSSs
(obviously I have a number of them) are the only place where I have any
styles.

Now I am writing a page that needs a few extra rules, almost certainly
one-off, and I don't want them in the normal CSS for that page layout. I'm
confident that the @import approach will work in most cases, but I believe
fails in NN4. A more logical approach would be to link to 2 CSSs from that
page, and as far as I can tell it is OK in my test set of browsers on W2000,
but I can't test on other platforms.

Using a style attribute would be another option. I have avoided styles within
my HTML pages so far, and would prefer to keep things that way. So I am trying
to find the best cross-browser, least-unsatisfactory, way of adding a few
specialist styles for that page.

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #38

P: n/a
Barry Pearson wrote:

I am writing a page based on a template that has a CSS. Lots of pages
use that CSS. This page needs some rules that are local to this page,
because of the special nature of its content, and I don't expect them
to used elsewhere.
<style type="text/css">
/* rules specific to this page here */
</style>

And link to the site-wide styles in the usual way.

Or,

<LINK REL="stylesheet" TYPE="text/css" HREF="site-wide.css"
MEDIA="screen">

<LINK REL="stylesheet" TYPE="text/css" HREF="this-page-only.css"
MEDIA="screen">

I have given this page its own CSS, which then uses @import for the
standard CSS for this template. As far as I can tell, this works OK,
although I believe this will not work properly in NN4, and will hide
the standard CSS.


Correct.

--
Brian (remove "invalid" from my address to email me)
http://www.tsmchughs.com/
Jul 20 '05 #39

P: n/a
Barry Pearson wrote:

I am writing a page based on a template that has a CSS. Lots of pages
use that CSS. This page needs some rules that are local to this page,
because of the special nature of its content, and I don't expect them
to used elsewhere.
<style type="text/css">
/* rules specific to this page here */
</style>

And link to the site-wide styles in the usual way.

Or,

<LINK REL="stylesheet" TYPE="text/css" HREF="site-wide.css"
MEDIA="screen">

<LINK REL="stylesheet" TYPE="text/css" HREF="this-page-only.css"
MEDIA="screen">

I have given this page its own CSS, which then uses @import for the
standard CSS for this template. As far as I can tell, this works OK,
although I believe this will not work properly in NN4, and will hide
the standard CSS.


Correct.

--
Brian (remove "invalid" from my address to email me)
http://www.tsmchughs.com/
Jul 20 '05 #40

P: n/a
Brian wrote:
Barry Pearson wrote: [snip] Or,

<LINK REL="stylesheet" TYPE="text/css" HREF="site-wide.css"
MEDIA="screen">

<LINK REL="stylesheet" TYPE="text/css" HREF="this-page-only.css"
MEDIA="screen">

[snip]

Thanks, that's what I'll go for. My worry was that would fail on some systems
I couldn't test on, but it appears OK. It is the logical approach for my
purpose. (I'm very wary of IE on Mac, because of bad experiences with the way
it handles some of my styles. It appears to defy logic at times,and since I
haven't got a Mac, I find out too late).

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #41

P: n/a
Brian wrote:
Barry Pearson wrote: [snip] Or,

<LINK REL="stylesheet" TYPE="text/css" HREF="site-wide.css"
MEDIA="screen">

<LINK REL="stylesheet" TYPE="text/css" HREF="this-page-only.css"
MEDIA="screen">

[snip]

Thanks, that's what I'll go for. My worry was that would fail on some systems
I couldn't test on, but it appears OK. It is the logical approach for my
purpose. (I'm very wary of IE on Mac, because of bad experiences with the way
it handles some of my styles. It appears to defy logic at times,and since I
haven't got a Mac, I find out too late).

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #42

P: n/a
Barry Pearson wrote:
Brian wrote:
<LINK REL="stylesheet" TYPE="text/css" HREF="site-wide.css"
MEDIA="screen">

<LINK REL="stylesheet" TYPE="text/css" HREF="this-page-only.css"
MEDIA="screen">
(I'm very wary of IE on Mac, because of bad experiences with the way
it handles some of my styles. It appears to defy logic at times,and
since I haven't got a Mac, I find out too late).


I think Mac is fussier with @import syntax than with LINK.

--
Brian (remove "invalid" from my address to email me)
http://www.tsmchughs.com/
Jul 20 '05 #43

P: n/a
Barry Pearson wrote:
Brian wrote:
<LINK REL="stylesheet" TYPE="text/css" HREF="site-wide.css"
MEDIA="screen">

<LINK REL="stylesheet" TYPE="text/css" HREF="this-page-only.css"
MEDIA="screen">
(I'm very wary of IE on Mac, because of bad experiences with the way
it handles some of my styles. It appears to defy logic at times,and
since I haven't got a Mac, I find out too late).


I think Mac is fussier with @import syntax than with LINK.

--
Brian (remove "invalid" from my address to email me)
http://www.tsmchughs.com/
Jul 20 '05 #44

P: n/a
Brian wrote:
Barry Pearson wrote:
Brian wrote:
<LINK REL="stylesheet" TYPE="text/css" HREF="site-wide.css"
MEDIA="screen">

<LINK REL="stylesheet" TYPE="text/css" HREF="this-page-only.css"
MEDIA="screen">

(I'm very wary of IE on Mac, because of bad experiences with the way
it handles some of my styles. It appears to defy logic at times,and
since I haven't got a Mac, I find out too late).


I think Mac is fussier with @import syntax than with LINK.


Thanks.

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #45

P: n/a
Brian wrote:
Barry Pearson wrote:
Brian wrote:
<LINK REL="stylesheet" TYPE="text/css" HREF="site-wide.css"
MEDIA="screen">

<LINK REL="stylesheet" TYPE="text/css" HREF="this-page-only.css"
MEDIA="screen">

(I'm very wary of IE on Mac, because of bad experiences with the way
it handles some of my styles. It appears to defy logic at times,and
since I haven't got a Mac, I find out too late).


I think Mac is fussier with @import syntax than with LINK.


Thanks.

--
Barry Pearson
http://www.Barry.Pearson.name/photography/
http://www.BirdsAndAnimals.info/
http://www.ChildSupportAnalysis.co.uk/
Jul 20 '05 #46

P: n/a
> That document is nearly two years old, has any further work been done
on this?
Would a W3C member (perhaps the editors of this draft) like to answer this question?

Or are you just trying to raise the dead?


I hope not.
Jul 20 '05 #47

P: n/a
> That document is nearly two years old, has any further work been done
on this?
Would a W3C member (perhaps the editors of this draft) like to answer this question?

Or are you just trying to raise the dead?


I hope not.
Jul 20 '05 #48

P: n/a
Markus Elfring wrote:
Would a W3C member (perhaps the editors of this draft) like to answer
this question?


What makes you think they particpate in this group? I don't recall ever
reading a comment from someone who said (admitted?)[1] that they are
part of the w3c.

[1] SCNR

--
Brian (remove "invalid" from my address to email me)
http://www.tsmchughs.com/
Jul 20 '05 #49

P: n/a
Markus Elfring wrote:
Would a W3C member (perhaps the editors of this draft) like to answer
this question?


What makes you think they particpate in this group? I don't recall ever
reading a comment from someone who said (admitted?)[1] that they are
part of the w3c.

[1] SCNR

--
Brian (remove "invalid" from my address to email me)
http://www.tsmchughs.com/
Jul 20 '05 #50

52 Replies

This discussion thread is closed

Replies have been disabled for this discussion.