Currently content viewer creates native widgets that aren't needed. We need to get rid of these. Kevin, is there already a bug for this? If so, mark this a dup.

Moving to M18

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.

Set milestone to mozilla0.9

travis is no longer @netscape.com changing qa contact to default for this component

I looked at the impact of the container widgets on WIN32. They have no noticable impact on performance and they have very little memory overhead (less than 1K of memory). On the Mac the container widgets are implemented as child windows and they also have very little impact on performance and memory.

Setting milestone to future. If it can be shown that these container widgets are causing severe performance problems on Linux than I'll reconsider changing the milestone.

This bug is blocking both print-preview and a DIGBug.

pushing out. This might change if we have to use native widgets.

Is this bug just for the removal of navtive widgets for views? This might be a red herring now that we're moving back toward allowing native form control widgets for embedded clients. In otherwords, removal may not be an option.

is this bug still valid?

Taking this bug

Build moving all existing future-P3 bugs to future-P4.