Pretius / Pretius-APEX-Enhanced-Lov-Item

Oracle APEX plugin
MIT License
24 stars 11 forks source link

Space white-space css #41

Open michele-pauluzzi opened 4 years ago

michele-pauluzzi commented 4 years ago

default

image

with white-space:pre-wrap; in the css

image

michele-pauluzzi commented 4 years ago

Fix: Css add

.pretius--enhancedLovItem.prompt > div.body  {
  white-space:pre-wrap;
}
.t-Form-fieldContainer--floatingLabel.is-active .pretius--enhancedLovItem.mask .tags {
  white-space:pre-wrap;
}

Js modified from

  tdAlign = this._popupColumnIsConfigurationAvailable( column_name, 'tdAlign' );
  tbodyTemplate += '<td class="t-Report-cell" align="'+tdAlign+'" headers="'+column_name+'">{{{'+column_name+'}}}</td>';
}

to

  tdAlign = this._popupColumnIsConfigurationAvailable( column_name, 'tdAlign' );
  tbodyTemplate += '<td class="t-Report-cell" style="white-space:pre-wrap;" align="'+tdAlign+'" headers="'+column_name+'">{{{'+column_name+'}}}</td>';
}
bostrowski commented 4 years ago

@michele-pauluzzi From what I've understood you want to fix the problem with white characters that are existing in your data.

You have introduced changes on three levels:

I can imagine the opposite situation when users don't want to have such behaviour for their data. In this case, I suggest changes on the plugin implementation level not on the plugin code.

For the autocomplete you should use cutom template and then use your own CSS rules which are specific for your use case scenario.

For popup report and tags just override CSS rules with your new rule on application/pages level.

At the moment I don't see the need to do changes in the plugin code.