Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#2778 closed defect (wontfix)

broken templateCssPath

Reported by: guest Owned by: bill
Priority: high Milestone:
Component: Widgets Version: 0.4.2
Keywords: Cc: [email protected]
Blocked By: Blocking:


Two ways for set own css to widget - templateCssString and templateCssPath. In 0.4.2 templateCssPath was broken in some widgets. In this widgets DEFAULT templateCssPath was removed and default css code placed to templateCssString (as i understand, for speed optimize). In DomWidget? the following logic - use templateCssPath only if templateCssString empty. As result, when i use my own templateCssPath, it's ignored, because already templateCssString set in widget's code. Sorry, if duplicate =(

Change History (4)

comment:1 Changed 15 years ago by bill

Resolution: invalid
Status: newclosed

Some widgets use templateCssString rather than templateCssPath. If you extend those widgets and set templateCssPath, you need to set templateCssString to null, like this:

  templateCssPath: ...,
  templateCssString: null,

Anyway, all of this is removed in dijit; there is no path or string at all.

comment:2 Changed 15 years ago by guest

Resolution: invalid
Status: closedreopened

It's not work for me. If i say:

<div class="dojo-FisheyeList"

css for widget lost, but specified css file was not loaded.

comment:3 Changed 15 years ago by bill

Milestone: 0.9M2
Resolution: wontfix
Status: reopenedclosed

Oh, you are trying to change the CSS on a per-widget basis? I thought you were trying to make a new type of widget based on FisheyeList?. Anyway, the CSS handling for 0.9 is changed so this is no longer an issue.

comment:4 Changed 15 years ago by (none)

Milestone: 0.9M2

Milestone 0.9M2 deleted

Note: See TracTickets for help on using tickets.