Quick question:
With the embedding harnesses being built, shouldn't those be our new
"viewer" for testing? We have a lot of code (widgets, etc) that are
bloating our app _only_ for viewer. The harnesses have that code in
their app, not in the widget DLL.
Can we make the switch?
karnaze wrote:
> Viewer now delays (i.e. -d option) before writing the regression data
> for a page. Before it was delaying after writing the data. This gives
> incremental reflow more time on some pages and eliminates the bogus bbox
> differences. Viewer can now also accept a delay inside the file list
> (e.g. delay:=2 on a line would set the delay to 2 seconds for subsequent
> pages).
--
Mike Pinkerton
Mac Browser Weenie
[EMAIL PROTECTED] http://people.netscape.com/pinkerton
