Quilleditor eigene Buttons erstellen, die ein div um den text mit einer klasse machen

import * as Quill from 'quill';
let Inline = (Quill as any).import('blots/inline');

(Quill as any).register(class extends Inline{
  static blotName = 'spanblock';
  static tagName = 'div';  static create(value){  let node = super.create(); node.setAttribute('class',this.blotName);    return node;  }
});
.....


export class ....
ngOnInit() {
  this.modules = {
     toolbar: [
       ['spanblock',.....

dann noch die css:

/**für alle (dynamischen) Buttons in der toolbar**/
quill-editor .ql-toolbar .ql-formats button:after {
  color:black;
  line-height: 19px;
  display: inline;
  position: relative;
  bottom: 4px;
}
quill-editor .ql-toolbar .ql-formats button{
  background-color: #F8F8F8;
  border: 1px solid #CCC;
  line-height: 19px;
  padding: 6px 10px;
  border-radius: 3px;
  margin: 15px 0;
  width:initial;
}

/**speziell der Button*************/
quill-editor .ql-toolbar .ql-formats button.ql-spanblock:after{
  content:"wichtig";
  font-weight: bold;
}

 

 

https://stackoverflow.com/questions/49247878/how-to-add-css-class-to-a-quill-selection

iis fehler in der Entwicklung

zeigte nichts mehr an und machte immer einen redirect auf accounts login…

https://stackoverflow.com/questions/5009565/asp-net-mvc3-and-windows-auth-on-iis-keeps-redirecting-to-account-login

Eine Lösung, die hier funktioniert hat ist:

I fixed it this way
1) Go ot IIS
2) Select your Project
3) Click on „Authentication“
4) Click on „Anonymous Authentication“ > Edit > select „Application pool identity“ instead of „Specific User“.
5) Done.

web workers mit parametern

As you can see you have the same mechanism for both worker-to-main and main-to-worker messages.

  • the postMessage method for sending messages
  • the onmessage member for defining the handler that receives the messages

In the main script:

worker.postMessage(data);

In the worker script:

self.addEventListener("message", function(e) {
    // the passed-in data is available via e.data
}, false);

… or just…

onmessage = function(e) {
    // the passed-in data is available via e.data
};