-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
Hidden paragraph BCD data still exists in content and in code #2228
Comments
@nschonni Let's tackle this one once we've taken care of all the excess |
It's clearly still there a lot:
|
I think this has to stay open until all are removed. I think it is my fault if it has been closed as I linked PR #5330 to it, even if it is a partial fix. |
Clearly some have been removed compared to by Feb 9 comment above:
|
Bha! What's going on. I didn't mean for this to be closed. Sorry. |
I noticed that it was near 1400 yesterday, meaning it was climbing. That's why I started removing them. I guess people are cloning pages than modifying them. |
We have removed the hidden paragraph BCD data from mdn/content. This 2 are not from such paragraph but from the contribute area explaining how to put compatibility tables in page. @peterbe Is there still something to do here, or can we close this issue? |
There might be some manual searching where it has minor spelling differences that the python script can't pick up. |
I ran the script with different needles, and manually fixed the remaining issues. :-), so I'm fairly confident for mdn/content. I'm a bit afraid to look at the size of mdn/translated-content :-) |
Let's now redirect to mdn/translated-content#1008 |
I’m closing this here because per #2228 (comment) it seems to be resolved for the mdn/content repo — and because the follow-up issue for that mdn/translated-content repo has been raised at mdn/translated-content#1008. But if I’m mistaken and this should in fact remain open, then somebody please do go ahead and re-open it. |
In mdn/yari#1191 we made the text:
be something that's part of the
<BrowserCompatibilityTable>
component. So every appearance of it in the content is redundant. This issue is about cleaning this up from the content.The text was updated successfully, but these errors were encountered: