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 94029 - show fragments styled using a style context from a page including it
Summary: show fragments styled using a style context from a page including it
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-02 19:23 UTC by bugbridge
Modified: 2007-05-31 19:21 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-02 19:23:31 UTC
Original status: 3-Accepted; Suggested Status: NEW


Description:
Page Fragments don't have their own associated stylesheets - after all a 
fragment can be included in different pages that each have their own 
stylesheet.

However, in common scenarios you -do- have a single stylesheet, and you'd have 
an improved WYSIWYG experience if this stylesheet was applied to the fragment 
when editing it as well.

This obviously can't include other inherited style content, as when a fragment 
is included a tag which for example sets an inherited CSS property like the 
text color. It should however pick up styles from the <head> section in a 
representative document. Or perhaps  users can choose the design-time context 
page to use via the document-properties when the fragment background is 
selected?

See http://swforum.sun.com/jive/thread.jspa?threadID=50292 for more discussion.

Evaluation:
Yes, there should be an option for the fragment which context page to use to 
inherit the stylesheets from or whether to use any at all.
Comment 1 Peter Zavadsky 2007-05-31 19:20:10 UTC
Again, it seems to be an issue with positioning of floats.
Comment 2 Peter Zavadsky 2007-05-31 19:21:01 UTC
Ignore the previous comment, it belongs to different issue.