problem: The Go button for Search has an arrow pointing to the upper right corner of the button instead of the word "Go"

(note on bugs #2960, #2961, #2963 and #2965. -- www.ibm.com) By the way ... www.ibm.com dynamically generates *every* page, both server-side and with all kinds of client-side javascript (including pixel-specific fragments driven by OS, browser, and version). (Look at the HTML source and it is echoing your user-agent, dns and exact time). If I save what 4.5 gets to disk and load it into nglayout, I get pretty good agreement in the two pages including 1) having the 'Go' instead of the 'arrow', 2) getting the background color, 3) getting the text box. (There are a couple of quirks: 1) small <input> box but that's a <style> issue, and 2) wrong color for <A> (blue not white) .. don't know why).

Using build dated 3/3 on win95 the Go button is OK now, but page has changed QA Contact please recheck too.

I am resolving this bug as INVALID for two reasons. First, it seems that this was at most a problem with IBM's javascript and the way they serve content based on variables such as user agent and such(see comments by 3jrgm@qlink.queensu.ca). This is typical as we transition to a new browser. Secondly, the problem doesn't seem to occur anymore. I'll resolve it INVALID now and then wait a day or two for comments before I VERIFY it as such.

I am resolving this bug as INVALID for two reasons. First, it seems that this was at most a problem with IBM's javascript and the way they serve content based on variables such as user agent and such(see comments by 3jrgm@qlink.queensu.ca). This is typical as we transition to a new browser. Secondly, the problem doesn't seem to occur anymore. I'll resolve it INVALID now and then wait a day or two for comments before I VERIFY it as such.

Thanks for resolving, Claudius. We're (esther) just helping out Beth with the top sites parity testing and reporting the differences we see. Since this is in your area of testing, if you concur with 3jrgm@qlink.queensu.ca's findings and feel this bug is invalid, then that's fine with us. Thanks.

Marking Verified since you'all agree :-)

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.