Closed Bug 427562 Opened 16 years ago Closed 16 years ago

specifications of item-categories with underline character in name do not show in sunbird 0.8

Categories

(Calendar :: Calendar Frontend, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: gerhard.mallot, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13pre) Gecko/20080331 Sunbird/0.8

[item-category="Ferien_DSG"]{
        color: blue !important;
        border-color: white !important;
        background-color: #00ffff ! important;
        border-width: 2px ! important;
        font-size: 4px ! important;
}


Reproducible: Always

Steps to Reproduce:
1. insert underline character in category name and restart
2.
3.
Actual Results:  
specifications for item category ignored

Expected Results:  
should show in sunbird 0.8 as in 0.7

Worked in sunbird 0.5 and 0.7. I just used the previous userChrome file and the special formatting for categories with underlines had disappeared after the upgrade to sunbird 0.8
In 0.8 the categories are now stored in encoded format to allow using non-ascii characters in categories names while using valid names for CSS rules. (see Bug 321010, Bug 355874, Bug 405356, Bug 412258).

According to my testing your category is stored as:

user_pref("calendar.categories.names", "Ferien_DSG");
user_pref("calendar.category.color.ferien-ux5f-dsg", "#FF0000");

Therefore you need to update your rules. The following might work:

  [item-category="ferien-ux5f-dsg"] .calendar-item { 
     border: solid white 2px !important; 
     background: blue !important; 
  } 
  [item-category="ferien-ux5f-dsg"] .calendar-item .calendar-event-selection { 
     border: none !important; 
  }

--> The change in 0.8 was done on purpose to fix e.g. the bugs mentioned above. I don't think this changes will be reverted therefore this bug is either Invalid or Wonfix.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Resolution: INVALID → FIXED
Changing to INVALID per comment#1.
Resolution: FIXED → INVALID
You need to log in before you can comment on or make changes to this bug.