progressmeter needs better default width/height values

VERIFIED FIXED

Status

()

P3
normal
VERIFIED FIXED
20 years ago
18 years ago

People

(Reporter: Brade, Assigned: german)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

20 years ago
Given the following in a xul file, I would expect to see 4 progressmeters which
are about 100% the width or height of the window.  I wouldn't be surprised if the
progressmeters appeared in some default width / height (such as 15 pixels by 100
pixels).  I *am* surprised that they (essentially) don't appear at all.

<?xml version="1.0"?>
<?xml-stylesheet href="resource:/res/samples/xul.css" type="text/css"?>

<window xmlns:html="http://www.w3.org/TR/REC-html40"
	xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
	width="300" height="300" onload="onLoad()">

 			  <progressmeter id="statusbar-icon" mode="normal" value="1" />
  <html:br/>
 			  <progressmeter id="undetermined.hprog"/>
  <html:br/>
			  <progressmeter id="vert.progress" value="1" align="vertical"/>
  <html:br/>
			  <progressmeter id="undeter.vprogress" value="1" align=
"horizontal"/>
</window>

Updated

20 years ago
Status: NEW → ASSIGNED
Target Milestone: M7

Updated

20 years ago
Assignee: evaughan → german
Status: ASSIGNED → NEW

Comment 1

20 years ago
A few things. Number one there was an error in the setup of you xul file this
caused a problem. The second problem is you set the current value of the
progress meter to be 1. That means 1% so there it only draws 1 pixel of the bar.
This is compounded by the fact that the the style German has set up for the
progress meter has no borders and no background. So If you don't have a bar to
display you will see nothing. That is how the style is set up. Perhaps we should
at least have a border around it. The style also gives it a default height of
0.7em which is a rather small height. If this is not set the default height is
16pixels. German can you fix this in CSS? You set the height to be 0.7em but
what if the progress meter is vertical? I don't think you want its height to be
0.7em. You would want its width to be 0.7em instead. Try removint the height
definition in progress meter and then run the following test. See how it works
and then change the style rules to get what you want:

<?xml version="1.0"?>
<?xml-stylesheet href="xul.css" type="text/css"?>
<?xml-stylesheet href="navigator.css" type="text/css"?>

<!DOCTYPE window>

<window style="width: 100%; height: 100%"
xmlns:html="http://www.w3.org/TR/REC-html40"
        xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
        onConstruction="Startup()">

        <progressmeter mode="normal" value="50%" />
		<html:br/>
        <progressmeter id="undetermined.hprog"/>
        <html:br/>
        <progressmeter id="vert.progress" value="75%" align="vertical"/>
        <html:br/>
        <progressmeter id="undeter.vprogress" value="25%" align=
"horizontal"/>
</window>

Comment 2

20 years ago
how critical is this for m7?

Updated

20 years ago
Target Milestone: M7 → M8

Comment 3

20 years ago
move to m8 after conversation with german.

Comment 4

20 years ago
Moving all Widget Set bugs, past and present, to new HTML Form Controls
component per request from karnaze.  Widget Set component will be retired
shortly.

Updated

20 years ago
Blocks: 8640
(Assignee)

Updated

20 years ago
Status: NEW → ASSIGNED
(Assignee)

Updated

20 years ago
Target Milestone: M8 → M9
(Assignee)

Comment 5

20 years ago
I need to move this to m9. Won't get to it before then
Also,there is no dependency to bug 8640 as listed here, since that bug 8640
deals with the splitter widget, which has nothing to with the progress bar.

Updated

20 years ago
No longer blocks: 8640
(Assignee)

Comment 6

20 years ago
as soon as the tree will go green I will put in this change:
progressmeter{
        display:inline;
        border: 1px inset white;
        color : #9999CC;
        background-color: grey;
}

progressmeter[align="horizontal"]{
        height: 1em;
}

that way vertical variations will work, and the common horizontal case should
display nicely inline with the font being chosen (height 1em)
(Assignee)

Comment 7

20 years ago
these changes are now checked in as of this morning. Feel free to re-open if
there's a problem.
(Assignee)

Comment 8

20 years ago
these changes are now checked in as of this morning. Feel free to re-open if
there's a problem.

Updated

20 years ago
QA Contact: phillip → ckritzer

Comment 9

20 years ago
QA Contact massive update.

Comment 10

19 years ago
This appears broken again.  I see what appears to be two vertical black bars,
the second slightly chopped...

Happens on:
- Linux6 2000-03-01-13 Commercial build
- MacOS9 2000-03-01-13 Commercial build
- Win98 2000-03-01-16 Commercial build

Comment 11

19 years ago
Dang, I forgot to reopen this earlier...

Also happens on:
- Linux6 2000-03-07-09 Commercial build
- MacOS9 2000-03-07-08 Commercial build
- Win98 2000-03-07-09 Commercial build
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 12

19 years ago
German,
Please update the TFV from M9, or dispose of this bug.
Thanks
(Assignee)

Comment 13

19 years ago
since progress meter is now box/xbl based it is no longer limited by the widget
default, now it can be set to anything by a xul designer. marking fixed
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 14

19 years ago
Re-opening bug.

Now nothing is being displayed on the screen.

For builds:
- MacOS9 2000-05-02-08-M15 Commercial
- Linux6 2000-05-02-08-M15 Commercial
- Win98  2000-05-02-08-M15 Commercial
Status: RESOLVED → REOPENED
OS: Mac System 8.5 → All
Hardware: Macintosh → All
Resolution: FIXED → ---

Comment 15

19 years ago
Move to later polish time. M20.
Target Milestone: M9 → M20
(Assignee)

Comment 16

19 years ago
This was fixed a long time ago right? Kathy, I assume we can close this bug since 
Eric's rewrite of progress meter has been completed?

Comment 17

19 years ago
Updating QA contact.
QA Contact: ckritzer → bsharma
(Assignee)

Comment 18

18 years ago
I am closing this bug assuming this was fixed with modern 2 redesign
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago18 years ago
Resolution: --- → FIXED

Comment 19

18 years ago
verifried build 2001081303 & 2001081308 os:win95,linux7.1,mac8.6
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.