Closed Bug 41839 Opened 24 years ago Closed 23 years ago

[wizards] cannot use non-html iframe in wizards.

Categories

(Core Graveyard :: Skinability, defect, P3)

Tracking

(Not tracked)

RESOLVED INVALID
Future

People

(Reporter: andreww, Unassigned)

References

Details

(Keywords: helpwanted, polish)

In trying to implement skinnability XUL changes, changing <html:iframe> to < iframe> (xul context) results in the following error: chrome://global/content/wizardHandlerSet.js line 155: window.frames[this.content_frame.name] has no properties Which breaks the wizard's ability to fetch form information and renders the wizard inoperable. See this in _all_ wizards like mailnews, find A buddy , aim migration, etc.
Many skinnability bugs in AIM depend on this.
Keywords: nsbeta2, skins
over to skinability component.
Assignee: don → ben
Component: XP Apps → Skinability
QA Contact: sairuh → szhu
cc myself
Putting on [nsbeta2-] radar. Not critical to beta2. Wizard skinnability not a beta2 stopper.
Whiteboard: [nsbeta2-]
M20
Target Milestone: --- → M20
Blocks: 42463
*spam* changing QA to me for all skinability bugs (all 4 of them!)
QA Contact: szhu → BlakeR1234
OS->All
OS: Mac System 8.5 → All
nav traige team: we are trying to cut skinning wizards (see bug 39336, also bug 41839) and have marked that nsbeta3- and Milestone Future. Doing the same for this one and reassigning to hangas, moving ben to cc.
Assignee: ben → hangas
Blocks: 39336
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3-]
Target Milestone: M20 → Future
Status: NEW → ASSIGNED
Adding nsbeta3 keyword to bugs which already have nsbeta3 status markings so the queries don't get all screwed up.
Keywords: nsbeta3
Is this a duplicate of Bug 39336, which has been fixed?
Is this a duplicate of Bug 39336, which has been fixed?
no, not the same as 39336, this is still an issue. the green lines have just been turned off at this point.
this blocks bugscape bug 1098.
Keywords: skins
nominating for nsbeta1 resetting the milestone for consideration.
Keywords: nsbeta1
Target Milestone: Future → ---
it's been 2 months since I nominated this for nsbeta1. is anyone going to triage this one?
I don't know, let's see if Ben does anything.
Assignee: hangas → ben
Status: ASSIGNED → NEW
Keywords: nsbeta2, nsbeta3
Whiteboard: [nsbeta2-][nsbeta3-]
Adding polish keyword, marking nsbeta1-. Not sure where I can stuff this in the schedule. Marked polish so that I put back onto post beta1 fix list, marked nsbeta1- because I don't think Ben will get to it for beta1.
Keywords: nsbeta1nsbeta1-, polish
Marking nsbeta1- bugs as future to get off the radar.
Target Milestone: --- → Future
QA Contact: blakeross → pmac
Mass move skinability bugs to nobody@mozilla.org, helpwanted.
Assignee: ben → nobody
Keywords: helpwanted
I don't think this is valid anymore with the new wizard.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.