Bug 130039 - Cannot remove property in Properties View
Summary: Cannot remove property in Properties View
Status: VERIFIED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.css (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M7   Edit
Assignee: Nitin Dahyabhai CLA
QA Contact:
URL:
Whiteboard:
Keywords: contributed
: 161666 (view as bug list)
Depends on:
Blocks: 219004
  Show dependency tree
 
Reported: 2006-03-01 17:24 EST by Amy Wu CLA
Modified: 2008-04-30 19:13 EDT (History)
2 users (show)

See Also:
thatnitind: review+

Attachments
Patch to remove CSS properties (2.17 KB, patch)
2008-02-21 13:03 EST, Nick Sandonato CLA 		bjorn.freeman-benson: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Amy Wu CLA 2006-03-01 17:24:10 EST 
1. Open CSS Editor
2. Go to a property in Properties view
3. click on "Remove Property" in Properties View toolbar

Nothing happens.  The property is not removed.  This seems to work fine in other editors like XML, HTML
Comment 1 Amy Wu CLA 2006-10-20 12:38:05 EDT 
*** Bug 161666 has been marked as a duplicate of this bug. ***
Comment 2 Nick Sandonato CLA 2008-02-21 13:03:46 EST 
Created attachment 90377 [details]
Patch to remove CSS properties
Comment 3 Nick Sandonato CLA 2008-04-04 14:58:35 EDT 
Submitting patch for review.
Comment 4 Nitin Dahyabhai CLA 2008-04-10 01:31:48 EDT 
Applied, thanks, Nick!
Comment 5 David Williams CLA 2008-04-24 00:45:25 EDT 
mass change to add 'contributed' keyword based on bugzilla query, please correct if that's not accurate (by marking patches as obsolete and removing the 'contributed' keyword.
Comment 6 Amy Wu CLA 2008-04-30 19:13:53 EDT 
Verified this bug is fixed for the most part in wtp3.0M7 20080424170254 sdk
I did find funny behaviour when I mixed and matched entering a property in manually versus using the properties view and then deleting it.  I opened bug 229738 for that issue.