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.

Sign up for GitHub

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

Jump to bottom

Chore(global) deprecate 'webspec' status support (closes #715) #742

Merged
merged 1 commit into from May 11, 2016
Merged

Chore(global) deprecate 'webspec' status support (closes #715) #742

merged 1 commit into from May 11, 2016

Conversation

marcoscaceres
Copy link
Member

No description provided.

@marcoscaceres
Copy link
Member Author

Bye bye "webspec", we hardly knew ye! 😢 👋

@marcoscaceres marcoscaceres mentioned this pull request May 9, 2016
Closed
@marcoscaceres
Copy link
Member Author

@tripu, all good to drop "webspec" status, right? My understanding is that it's not used on the w3c side.

cc @dontcallmedom.

@tripu
Copy link
Member

tripu commented May 10, 2016

@marcoscaceres:

AFAIK, we can get rid of webspecs, yes. But I'm not familiar with the internals of ReSpec, really.

Over to @dontcallmedom or @halindrome to triple-check.

@marcoscaceres
Copy link
Member Author

On 10 May 2016, at 8:42 PM, tripu notifications@github.com wrote:

@marcoscaceres:

Is examples/respec-debug.js regenerated automatically?

No. But will add a task to do that (or to delete it).

js/core/css/examples-webspecs.css mentions “EXAMPLES CONFLICTING WITH WEBSPECS”. Maybe the file is not necessary any more?
AFAIK, we can get rid of webspecs, yes. But I'm not familiar with the internals of ReSpec, really.

Over to @dontcallmedom or @halindrome to triple-check.

It's more of a question about if the Webspecs project died. It seems it did, but wanted confirmation.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@dontcallmedom
Copy link
Member

No objection from me (not that I have any particularly useful insights); that said, I think it would be nice in the future that before deprecating a type of document, we start with emitting warnings.

@tripu
Copy link
Member

tripu commented May 10, 2016

@marcoscaceres, I didn't know about Webspecs in ReSpec until I noticed that the CSS in modern-tooling was broken, so… :)

(What about editing js/core/css/examples-webspecs.css, then?)

@marcoscaceres
Copy link
Member Author

(What about editing js/core/css/examples-webspecs.css, then?)

I'll delete it instead, as it doesn't apply.

@marcoscaceres marcoscaceres merged commit 0dc9407 into develop May 11, 2016
@marcoscaceres marcoscaceres deleted the remove_webspec_stuff branch May 11, 2016 12:13
marcoscaceres added a commit that referenced this pull request May 18, 2016
@marcoscaceres
Merge branch 'develop' into gh-pages
0ad7d39 
* develop:
  v3.2.123
  Feat(markdown): teach markdown how to highlight code (#759)
  Fix(utils): correctly calculate leftPad + add toESIterable()
  Feat(text): update requirejs text.js (closes #763) (#764)
  Feat(domReady): update requirejs domReady (#765)
  Fix(respec2.css): Override code highlighter background (#758)
  Feat(global): add hightlighter and beautifier as deps
  Fixed an error in the test.
  Added a test for FrozenArray attributes
  Chore(global) deprecate 'webspec' status support (closes #715) (#742)
  chore(package): update promise-polyfill to version 5.1.0 (#743)
  chore(package): update command-line-usage to version 2.0.5 (#744)
  Feat (appveyor): enable appveyor (#727)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@tripu tripu

Labels
needs review
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@marcoscaceres @tripu @dontcallmedom