Using M13 Win32 build. Actual Results The text field's border and padding is overlapping (rendered inside) the field itself. Expected Results The border and padding should appear outside of the field.

Reassigning to Rod.

No, this is (strangely enough) the correct behavior for NavQuirks. The idea when laying out in NavQuirks is to be the same size as Nav. Nav does not handle this type of style, so we don't either for NavQuirks. If you then say, that we should never allow the border size to be greater than two so it would at least render nicely (and look like NavQuirks), then that is a reasonable request and maybe I could get it in for M15 or M16 It works correctly and as expected when in Standard mode.

I was expecting everything to be the correct size. The border and the widget not overlapping like it is. I'm not sure of the navquirks mode details and it's limitations, but it would be nice to be able to use CSS properties on widgets and have them work even if they are ugly. Never allowing the border to be increasd isn't the long term solution I hoped for, but neither is what it is doing now in the test case. If limiting the properties is the only way, it would be better.

Rereading the comment, it seems you are referring to compatibility with Navigator of 4.xx and it's CSS abilites (what little it has). I was under the impression that mozilla would be 100% CSS1 compliant.

Mozilla in "Standard" should be fully standards compliant, if not file a bug. When it is in NavQuirks mode, it does what little (or maybe a little more) than what Nav 4.x does. Switch the flafg in viewer or make sure your DTD is "Strict' and it will do the right thing.

setting to M16 and marking low priority

mass-move to M16

Moving out by executive order.

This is because the NavQuirks sizing assume zero padding and a two pixel border. When we have a NavQuirks style sheet we can make the padding and border !important and solve this.

nominating as nsbeta2 since the fix is a simple change to html.css now that the NavQuirk style sheet exists.

Can we see just how trivial this patch would be? We have lots of bugs, and can't afford regressions just now (running towards beta2).

Putting on [nsbeta2-] radar.

M16 has been out for a while now, these bugs target milestones need to be updated.

setting to M17

Marking nsbeta3+

This was fixed when the quirk.css was put in a while back. marking works for me.

Oops, that embarressing, it works for me because the change is in my tree. Reopening and and I will check the fix in today and then mark it fixed.

fixed

Marking VERIFIED FIXED on: - LinuxRH62 2000-09-07-08-M18 Commercial - Win98 2000-09-07-08-M18 Mozilla - MacOS86 2000-09-07-04-M18 Commercial

reopening because I am removing the fix.

marking won't fix.

See bug 55336 for the fix removal

Correct QA Contact -> vladimire

I'm verifying wontfix, although I dont see the problem....