This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 94101 - designer should not render dotted lines corresponding to div tags surrounding Table component
Summary: designer should not render dotted lines corresponding to div tags surrounding...
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Winston Prakash
Depends on:
Reported: 2007-02-02 20:38 UTC by bugbridge
Modified: 2007-07-11 23:10 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-02 20:38:09 UTC
Original status: 5-Cause Known; Suggested Status: NEW

Original Target Release: shortfin_dev; Suggested Target Milestone : 5.5

Components that generate HTML contained within an outer div tag are rendered in
the Creator designer with dotted lines surrounding them. This makes the
component difficult to parse visually, and makes the component look messy in the

If possible, I am proposing that Creator ignores (does not render) these div
tags at all in the designer.

For example, the buttons in the rebranded masthead component may be redesigned
so they are surrounded by div tags. In the designer, each button that renders in
the masthead will then be surrounded by a dotted line. The designer should
ignore these div tags, and just render the button code.

There is code in designer which renders so called designer border for such
components (div mostly).
It seems, that it is insufficient in designer to be able to decide when the
border should be painted and when not, it seems that designtime should provide
such information.

For now it probably needs to be there, otherwise page fragment, layout panel (or
some other) wouldn't be visible to the user.

Passing to designtime to consider/provide a solution, and also adding Dusan as
HIE to the interest list.

Evaluation (Entry 2):
Winston, don't assign this back, without providing any info. 
I am asking for a solution from designtime, which is missing now. Designer can't
decide based on nothing whether to draw or not draw the dotted border, the
designtime info for the component should say that.

Evaluation (Entry 3):
I see that this bug has recently been assigned to me, but I believe this was
intended as a general bug against Creator. For example, the brand changes
introduced a div tag around the button component, which did not display
correctly in Creator -- ultimately, we removed the div completely, partly
because of this issue. I only created a design-time renderer for the table
because the underlying issue has not been addressed in Creator. I consider the
design-time renderer as a work-around until this is corrected. If would prefer
to set a property rather than to change the output HTML. The rendered HTML is
vastly different than what is shown in the dsigner (e.g., IDs are not rendered
on the same HTML tags). Winston, if you feel that this will never be fixed in
Creator, then mark the bug as such.


Winston Prakash wrote:
> Hi Peter/Shura,
> Looks like <div> is placed around some of the components because of branding
and/or UI guidelines.
> I agree, having the dotted line around components may be a visual annoyance.
> One solution I could think of is - we provide  toggle button  similar to
show/hide virtual forms.
> The "Show border" toggle button could show or not show the dotted line based
on users choice.
> Does that make sense?
> - Winston

Evaluation (Entry 4):
I don't consider this as a p2 issue, as it does not break any functionalit but
just a visaul aid. So downgrading this to p3
Comment 1 Peter Zavadsky 2007-06-05 00:12:44 UTC
As stated above there is missing API (DesignTime API?) which would tell the
designer whether it should paint the so called design border around certain
components or not.
The designer can't decide based on the element structure only, as tries the
original implementation. In order to show the border around fragments, panels,
etc., it tries to find out based on the element structure.
But that can't work (unless it is checked and made more complicated every time
new component is added).
To solve it once and forever, the API (hint) for the component is necessary
instead of trying to create some kind of heuristic logic in the designer, there
is just not enough information.
Passing back.