Closed
Bug 301672
Opened 19 years ago
Closed 19 years ago
Breadcrumbs extension needs to use '.' in addition to ':' to seperate pages
Categories
(developer.mozilla.org Graveyard :: General, defect, P1)
developer.mozilla.org Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
Details
Attachments
(2 files, 1 obsolete file)
|
2.17 KB,
patch
|
reed
:
review+
|
Details | Diff | Splinter Review |
|
1.98 KB,
patch
|
reed
:
review+
|
Details | Diff | Splinter Review |
The breadcrumbs extension needs to also use '.' to seperate pages to facilitate window.open type page-names. This should not assume anything about "what comes later" to allow uses like: Gecko_DOM_Reference:window.open:page1 to link like Gecko_DOM_Reference > window > open > page1 patch forthcoming
| Assignee | ||
Comment 1•19 years ago
|
||
This should do it; See (temporarily hosted) http://drapostles.hypermart.net/test.php for a running copy of the biggest change here. and http://drapostles.hypermart.net/test.php.txt for source of the test file.
| Assignee | ||
Comment 2•19 years ago
|
||
See Bug 301677 for what I envision we can do once this is applied.
Priority: -- → P1
| Assignee | ||
Updated•19 years ago
|
Attachment #190103 -
Flags: review?(shaver)
Comment 3•19 years ago
|
||
Comment on attachment 190103 [details] [diff] [review] Allow '.' >+//Note this extension only works, as written for PHP version 4.0.5 and up > $wgExtensionFunctions[] = "mzBreadcrumbs"; Remove bogus comma, and explain what the specific dependency is that requires 4.0.5+. >+ //two array shifts here will grab the ":" and fixup $parts at the same time. Can you elaborate on "fixup" (and spell it as "fix up"), please? >+ for ($i =0; $i < count($parts ); $i+=2 ) { >+ if ( $i > 1 ) { Style in this file has spaces around operators ($i += 2), and not around predicates (if ($i > 1), while ($j < $i)). r=shaver with those nits fixed, thanks for taking care of this for me!
Attachment #190103 -
Flags: review?(shaver) → review+
| Assignee | ||
Comment 4•19 years ago
|
||
Shaver, thanks for checking in my first patch to get this stuff started, here is the patch correcting the review nits, when this gets checked in, you can resolve this bug. (or I can resolve)
| Assignee | ||
Updated•19 years ago
|
Attachment #191067 -
Flags: review?(shaver)
| Assignee | ||
Comment 5•19 years ago
|
||
Grr, damn comment typo...Thanks to Colin on #bmo for pointing it out to me.
Attachment #191067 -
Attachment is obsolete: true
Attachment #191069 -
Flags: review?(shaver)
| Assignee | ||
Updated•19 years ago
|
Attachment #191067 -
Flags: review?(shaver)
| Assignee | ||
Comment 6•19 years ago
|
||
Comment on attachment 191069 [details] [diff] [review] Fix Review Nits (for real) Dria poked at these review nit fixups for me, and comitted the file to cvs.
Attachment #191069 -
Flags: review?(shaver) → review+
| Assignee | ||
Updated•19 years ago
|
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Component: developer.mozilla.org → Infrastructure
Flags: review+
Product: mozilla.org → Mozilla Developer Center
QA Contact: qa → infrastructure
Version: other → unspecified
Updated•19 years ago
|
Attachment #190103 -
Flags: review+
Updated•19 years ago
|
Attachment #191069 -
Flags: review+
Updated•12 years ago
|
Component: Deki Infrastructure → Other
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
•