scottputterman Reporter
	Description • 25 years ago

bug tracking feature in Summary.

	scottputterman Reporter
	Comment 1 • 25 years ago

Setting Target M14

	(not reading, please use seth@sspitzer.org instead)
	Comment 2 • 25 years ago

accepting.

	Phil Peterson
	Comment 3 • 25 years ago

*** Bug 26056 has been marked as a duplicate of this bug. ***

	selmer (gone)
	Comment 4 • 25 years ago

Sol, move back to M16 if we can't live without this in beta2.

	selmer (gone)
	Comment 5 • 25 years ago

[FEATURE] bugs past M16 are OUT for this release.  Marking M20.  If you disagree 
with this action, please help me explain it to the PDT.

	lchiang
	Comment 6 • 24 years ago

Moving feature bugs to target milestone "Future" for next release consideration.

	Matthew T (active 1999-2002)
	Comment 7 • 24 years ago

Jag, wanna take this?

	Peter "jag" Annema Assignee
	Comment 8 • 24 years ago

I can take a stab at this.

	Peter "jag" Annema Assignee
	Comment 9 • 24 years ago

This depends on bug 57984 and rewriting the menu to be an overlay.

	Peter "jag" Annema Assignee
	Comment 10 • 24 years ago

Yay, I have a prototype working now. The menu, accel +/-, it all works, with
maximal code sharing between navigator and mail/news (though that should really
be turned around. Once I had my ZoomManager JS object and support code written
and all neatly in an overlay, adding it to mail/news was only a few lines.)

Next up is adding it to Composer and see if that goes just as well.

	Peter "jag" Annema Assignee
	Comment 12 • 24 years ago

I'm putting this here to get some peer review on what I'm doing there. I want to
replace the <box id="stringbundleset"/> with a <stringbundleset
id="stringbundleset"/>, but at this point adding this overlay to mail/news
requires as less as adding that <box>, a <menuitem>, and a function
getMarkupDocumentViewer() (and the overlay, of course).

	scottputterman Reporter
	Comment 13 • 24 years ago

Seth or Bhuvan, could you give feedback on this first patch?

	Peter "jag" Annema Assignee
	Comment 14 • 24 years ago

I've created a new bug (bug 64449) to track moving this code into its own
overlay, marking this depend on it.

	Peter "jag" Annema Assignee
	Comment 15 • 24 years ago

Bug 64449 is fixed, working on this part now.

	Peter Lairo
	Comment 18 • 24 years ago

Any idea when this will show up in the next nightly?

	Peter "jag" Annema Assignee
	Comment 19 • 24 years ago

Well, as soon as I get r=, sr=, and an open tree :-)

Anyone on the cc list wanna r= / sr=? :-)

	timeless
	Comment 20 • 24 years ago

r=timeless [w/ whitespace variance]

	(not reading, please use seth@sspitzer.org instead)
	Comment 21 • 24 years ago

jag, can you explain the change from <iframe ...> to <browser ...> in the patch?

	Ben Goodger (use ben at mozilla dot org for email)
	Comment 22 • 24 years ago

The <browser/> element is a rich iframe capable of offering the same drag & drop, 
HTML TITLE tooltip etc capabilities of the Navigator content area. The browser 
XBL widget is currently in construction but when it is complete all this 
functionality will be had for free simply by replacing an iframe with a browser. 
Clients are then able to customize the widget by adding their own context menu 
(which overrides the default), etc. 

	(not reading, please use seth@sspitzer.org instead)
	Comment 23 • 24 years ago

update:  jag is double checking something for me (about the iframe -> browser
change).

	Peter "jag" Annema Assignee
	Comment 24 • 24 years ago

Change from iframe to browser seems safe (e.g. no one doing
getElementsByTagName("iframe") or something like that). Attaching new patch
which caches the messagepane element.

	(not reading, please use seth@sspitzer.org instead)
	Comment 26 • 24 years ago

sr=sspitzer

(note to jag, that patch contains a fix for another bug)

	timeless
	Comment 27 • 24 years ago

r=timeless

	Peter "jag" Annema Assignee
	Comment 28 • 24 years ago

Checked in, marking fixed.

	stephend@netscape.com (gone - use stephen.donner@gmail.com instead)
	Comment 29 • 24 years ago

Jag, this menu item works fine on Windows 2000 build 2001020504 and Linux build
2001020506, but it's not even present on my Mac build 2001020513.

Right after View | Headers, there are two seperators.  Is something just missing
in an overlay file?

	Peter "jag" Annema Assignee
	Comment 30 • 24 years ago

Nope... Mac doesn't do this menu yet, and in the browser I chucked this in an
existing section and could just hide the menu item. In Mail/News it looks like
I'll need to add some logic to hide the separator I had to add.

Patch coming up.

	stephend@netscape.com (gone - use stephen.donner@gmail.com instead)
	Comment 32 • 24 years ago

I can't pull on Mac, but I'll get this verified tomorrow.  Thanks Jag.

	Blake Ross
	Comment 33 • 24 years ago

r=blake

	(not reading, please use seth@sspitzer.org instead)
	Comment 34 • 24 years ago

sr=sspitzer on the patch from jag on 2001-02-05 16:28 

	Peter "jag" Annema Assignee
	Comment 35 • 24 years ago

Fix checked in, marking fixed once more.

	stephend@netscape.com (gone - use stephen.donner@gmail.com instead)
	Comment 36 • 24 years ago

VERIFIED, build 2001021408 doesn't have this menu item present (nor the extra
seperator.)