Closed
Bug 776139
Opened 12 years ago
Closed 12 years ago
Kuma: If you build a link to a non-existent page on a non-English locale, with the query to edit the page, you get the en-US page anyway
Categories
(developer.mozilla.org Graveyard :: Wiki pages, defect)
developer.mozilla.org Graveyard
Wiki pages
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: sheppy, Unassigned)
Details
Go to https://developer-new.mozilla.org/it/docs/Guida_di_riferimento_ai_CSS See the link to overflow-wrap? That's not what you should get when you do cssxref to generate that link. See the template here: https://developer-new.mozilla.org/en-US/docs/Template:Cssxref
Comment 1•12 years ago
|
||
Sheppy: Template noob here. Could you elaborate on "not what you should get when you do cssxref to generate that link"? What should that link look like instead?
Reporter | ||
Comment 2•12 years ago
|
||
Whoa. It's working correctly now. That's weird.
Comment 3•12 years ago
|
||
(In reply to Eric Shepherd [:sheppy] from comment #0) > Go to https://developer-new.mozilla.org/it/docs/Guida_di_riferimento_ai_CSS > > See the link to overflow-wrap? That's not what you should get when you do > cssxref to generate that link. See the template here: > > https://developer-new.mozilla.org/en-US/docs/Template:Cssxref What was the issue, specifically? Since it's working correctly now, I can't look at the link to overflow-wrap as an example of the issue. Maybe something else fixed this?
Comment 4•12 years ago
|
||
Resolving as WORKSFORME (really WORKSFORSHEPPY). Sheppy: If you get a chance, can you answer comment 3? Just want to be sure there isn't something else going on here.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•12 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•12 years ago
|
Version: Kuma → unspecified
Assignee | ||
Updated•12 years ago
|
Component: Website → Landing pages
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•