It doesn't support css borders and padding. To do this you will need a pair of frames: an outer frame and an inner frame. The inner frame will contain either the plugin or some frame to manage the object's contents when the plugin is unavailable. The outer frame will take care of the borders.
Can you take a look at this, Andrei? You might want to meet with Kipp to discuss exactly what needs to be done.
Moving this to P1 since plugins won't display correctly until this is fixed. I haved checked in a temporary workaround so that plugins at least display for now.
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
reassigning to Greg Lynn as QA contact
Kipp please provide test case. QA assigned changed to white box lead.
What's the status of this bug?
Do we have a test case?
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Am I correct in inferring that this means that OBJECT won't support the CSS1 styles mentioned?
Justification for loss of future: css1 relnote2: if we don't fully support css we need to say so. nsbeta3: css1
All: This bug report is too cryptic; I don't understand what it means. Is it saying that the OBJECT tag will fail to support certain CSS properties? timeless: Many thanks for your concern and help. A few requests: 1) If someone has indicated that this bug is to be left as-is for FCS and postponed for Future reconsideration by marking that bug Future, please do not remove the Future marking unless you yourself or another mozilla community member are accepting the bug and taking responsibility for fixing it by a particular milestone. Basically, if you're committing to do the work, you're free to set the milestone; if not, changing it from Future to -- loses valuable information (the fact that this is not a "new no milestone" bug, but one that's been evaluated and passed on) and creates more work for others. 2) To evaluate your nsbeta3 nomination, we need more than just a statement that this is a "css1" issue. Not all css1 issues (or all bugs of any kind, for that matter) will be fixed before N6 FCS; there will be release notes. To prioritize, we need to know the user/developer impact. Restoring FUTURE until someone takes responsibility for fixing this, marking [NEED INFO]. Recommend nsbeta3- unless we get a convincing statement of customer/developer impact.
Marking as [nsbeta3-] a number of bugs that were already marked Future (but not [nsbeta3-]) because the Netscape engineer the bug is assigned to is overburdened. If you disagree with this decision, please provide information about customer and user impact, but please do not clear the [nsbeta3-] unless you are reassigning the bug to yourself and committing to a fix within the nsbeta3 timeframe.
I'm not sure what the bug is documenting either. I just tested borders and padding with the OBJECT element, and they appear to be working fine. Marking WORKSFORME. If anyone wants to reopen, *please provide a test case*.