Re: Verification Culture

2012-08-12 Thread Robert Kaiser

Jason Smith schrieb:

Note - I still think it's useful for a QA driver to look through a set
of bugs fixed for a certain Firefox release, it's just the process would
be re-purposed for flagging a bug for needing more extensive testing for
X purpose (e.g. web compatibility).


I think QA should do some exploratory testing of major new features as 
time allows, but just verifying existing test cases that often are 
running automatically anyhow isn't a good use of time, I guess.


Robert Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: WheelEvent of DOM Level 3 Events now landed

2012-08-12 Thread Neil

Masayuki Nakano wrote:

By the changes, some prefs of mousewheel.* don't make sense now. They 
are replaced with new prefs:


* 
mousewheel.(horizscroll.)?(withshiftkey|withaltkey|withmetakey|withcontrolkey|withnokey).sysnumlines


Just removed.

* 
mousewheel.(horizscroll.)?(withshiftkey|withaltkey|withmetakey|withcontrolkey|withnokey).numlines


Replaced with

mousewheel.(default|with_shif|with_alt|with_control|with_meta|with_win).delta_multiplier_(x|y|z)

New prefs' value multiplies deltaX, deltaY or deltaZ of wheel
event. 100 means 1.0 but values less than 100 and larger than -100
are not allowed.

* 
mousewheel.(horizscroll.)?(withshiftkey|withaltkey|withmetakey|withcontrolkey|withnokey).action


Replaced with

mousewheel.(default|with_shif|with_alt|with_control|with_meta|with_win).action

New pref's value are:

   0. Nothing happens
   1. Scrolling contents
   2. Go back or go forward, in your history
   3. Zoom in or out.

You cannot specify different actions to X and Y since a wheel
event can have non-zero values to both deltaX and deltaY
attributes same time.

Any new pref names are not same as old pref names. I.e., users need to 
customize them again but users can share the customized settings 
between ESR10 and Mozilla 17 or later.


So, as far as SeaMonkey's Mouse Wheel pref pane goes, do I understand 
correctly that we have to remove the vertical/horizontal scrolling 
distinction, we have to remove the Scroll a page option and add a Do 
Nothing option, and we have to change the Scroll by [N] lines somehow 
- this bit I'm not sure about, it seems as if you can't make the wheel 
scroll more slowly any more?


--
Warning: May contain traces of nuts.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Verification Culture

2012-08-12 Thread Nicholas Nethercote
On Fri, Aug 10, 2012 at 2:04 PM, Jason Smith jsm...@mozilla.com wrote:
  * Flagging of a risky patch needing to be sure it works - This is
where doing a deep dive generally by formulating a test plan and
executing it is useful.

This suggestion reminds me of the fact that members of the JS team
occasionally ask Jesse/Gary/Decoder to run their JS fuzz tools over
risky patches.  This works well in practice -- the fuzz tools often
find problems.

Running an automatic tool is of course easier than formulating a
human-based plan, but it's still a good precedent.

Nick
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform