- From: <bugzilla@jessica.w3.org>
- Date: Fri, 21 Oct 2011 16:24:10 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12943 Lucas Sa <lucas.sa@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NEEDSINFO | --- Comment #8 from Lucas Sa <lucas.sa@gmail.com> 2011-10-21 16:24:08 UTC --- Sorry for the very late response, I couldn't follow up the bug. > I don't agree that percentage is better than position, nor that completion is. > It's not a percentage if it's not out of a 100 (which it isn't, it's a fraction > 0..1). The progress bar is not a percentage; almost always the max will be some > number other than 100, e.g. in a file transfer it would be the file size, in a > long calculation it would be the number of steps, etc. Completely disagree. The position is a number between 0..1, which may represent a percentage (0% to 100%) whether the max is 100 or not. 100% = 100/100 = 1. > The term "position" is the right term of art here; see e.g. reference [2] in > comment 2 which refers to the position of the progress bar in the > documentation. Also disagree. In reference [2], the term "position" refers to the absolute position (or the Value attribute in our case), i.e., if max=200 and value=100 the position as specified in [2] is 100, not 0.5 (or 50%?), which is the case of our "position". Thus, for me, the term of art "position" that you refer to is the absolute position and, in the specification, it is actually a relative position. See http://en.wikipedia.org/wiki/Relative_change_and_difference [4] -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 21 October 2011 16:24:12 UTC