Please report any other irregularities here.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20060728 Firefox/22.214.171.124 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060823 Calendar/0.3a2+ when you delete all categories and try to create new event except predefined None category there is another one - blank (empty) Reproducible: Always Steps to Reproduce: 1. delete all categories from option 2. create new event 3. press dropdown list to choose category -> there is one more empty category 4. select this empty category and press ok to accept 5. reopen created event -> category is set to None 6. go back to category list in option -> some empty category was created in meantime Actual Results: - empty category was created in meantime without my knowledge - created category is treated as None for new events Expected Results: category list should be empty - there is one predefined category None for new events errror console is empty might be defect after changes in bug 342341
(In reply to comment #0) I can confirm it with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061027 Calendar/0.4a1 > Expected Results: > category list should be empty - there is one predefined category None for new > events I found an error when I tried to edit the new 'none' category: 1. After 6th step click edit button 2. Look in error console: Warning: Expected color but found 'null'. Error in parsing value for property 'background-color'. Declaration dropped. Source File: chrome://calendar/content/preferences/editCategory.xul Line: 0
Status: UNCONFIRMED → NEW
Ever confirmed: true
The behavior was changed with Bug 402534 for the 0.8 release to allow localized categories names in Lightning too. If you now delete all categories the list of categories will be set back to the default ones next time you access it. Therefore the issue reported doesn't exist anymore.
Resolving as INVALID per comment#3.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.