Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extraCSS has no effect #271

Closed
dirkschulze opened this issue Sep 22, 2013 · 8 comments
Closed

extraCSS has no effect #271

dirkschulze opened this issue Sep 22, 2013 · 8 comments

Comments

@dirkschulze
Copy link
Contributor

Adding the following lines to the meta section at the beginning has no effect at all:

      extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css",
                 "https://dvcs.w3.org/hg/FXTF/raw-file/tip/masking/default.css"],
@dirkschulze
Copy link
Contributor Author

I just read the comment from style.js

The extraCSS configuration option is now deprecated. People rarely use it...

I think I disagree with this phrase. It just happens that people do not update to frequently and use an older version of the tool. I just ran into the trap myself.

There are fairly good reasons to support other styles. Not every WG has the same style conventions and may adapt the W3C style to own needs.

@darobin
Copy link
Member

darobin commented Sep 23, 2013

Hi @dirkschulze!

This has been deprecated for a long time and is documented (http://www.w3.org/respec/ref.html#extracss). Few people use an old version of ReSpec because most link to the canonical URL — which is really the right thing to do, using local copies is strongly discouraged.

Additionally, one of the reasons for deprecating extraCSS was that most people were using it wrong. In your example above, you would load the outdated ReSpec v1 CSS in addition to the one that ReSpec normally provides. That would cause not just useless content to be added, but almost certainly some bugs too.

Furthermore extraCSS, though rarely used, when it was regularly had problems with groups publishing to TR while linking to an external style, or bumped into SOP limitations.

The recommend way of adding your own styles is now to rely on <link href>. And please stop using a local copy!

@darobin darobin closed this as completed Sep 23, 2013
@dirkschulze
Copy link
Contributor Author

You can hardly blame someone for following the documentation :). The pasted example is from the documentation . Since it seems not only deprecated but also not functional, it might be time to remove the last mentioning of it from the source code.

<link href.. worked fine and exactly as expected. This could be added as note to the documentation instead of still mentioning extraCSS without any indication of deprecation.

@fhirsch
Copy link
Contributor

fhirsch commented Sep 23, 2013

agree with this. why deprecate it?

On Sep 22, 2013, at 4:10 PM, Dirk Schulze notifications@github.com wrote:

I just read the comment from style.js

The extraCSS configuration option is now deprecated. People rarely use it...

I think I disagree with this phrase. It just happens that people do not update to frequently and use an older version of the tool. I just ran into the trap myself.

There are fairly good reasons to support other styles. Not every WG has the same style conventions and may adapt the W3C style to own needs.


Reply to this email directly or view it on GitHub.

@fhirsch
Copy link
Contributor

fhirsch commented Sep 23, 2013

ah, thanks for the explanation Robin. So we can update styles but via a different mechanism (now to think of it, I think I did use link href..

On Sep 23, 2013, at 6:05 AM, Robin Berjon notifications@github.com wrote:

Hi @dirkschulze!

This has been deprecated for a long time and is documented (http://www.w3.org/respec/ref.html#extracss). Few people use an old version of ReSpec because most link to the canonical URL — which is really the right thing to do, using local copies is strongly discouraged.

Additionally, one of the reasons for deprecating extraCSS was that most people were using it wrong. In your example above, you would load the outdated ReSpec v1 CSS in addition to the one that ReSpec normally provides. That would cause not just useless content to be added, but almost certainly some bugs too.

Furthermore extraCSS, though rarely used, when it was regularly had problems with groups publishing to TR while linking to an external style, or bumped into SOP limitations.

The recommend way of adding your own styles is now to rely on . And please stop using a local copy!


Reply to this email directly or view it on GitHub.

@darobin
Copy link
Member

darobin commented Sep 23, 2013

@dirkschulze Which documentation? If I grep through the documentation for extraCSS, I find two mentions. One is the definition at http://www.w3.org/respec/ref.html#extracss which starts with the word "Deprecated", the other is from http://www.w3.org/respec/guide.html#extra-styling and says "In some old documents, you will on occasion find an extraCSS configuration option. Do not use it, it is deprecated."

Is there any chance you also have a local copy of the old documentation?

@dirkschulze
Copy link
Contributor Author

There was a document that explained all possible meta information like noIDLSorting in detail. I can indeed not find it anymore which is sad :(.

The document http://www.w3.org/respec/guide.html is interesting so but not in my copy of the repository.

@darobin
Copy link
Member

darobin commented Sep 26, 2013

That documentation was seriously outdated though. It is still missing some bits, but making progress, and the bits that are there are far more accurate.

You can check out the respec-docs repository to get it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants