-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editor! #58
Conversation
Specifically, we have cases where selecting nodes with no children results in an ambiguous offset. Technically, these represent annotation boundaries, but since we don't actually want to disambiguate these, we're instead looking at pure textual offsets. The major change here was simplifying the code that handles selection on nodes with no children (cf, <hr>, <img>) and nodes that are outside the text selection component.
…have lost the original DOM tree / selection
…(deletion/update of annotations TK)
Specifically, we have cases where selecting nodes with no children results in an ambiguous offset. Technically, these represent annotation boundaries, but since we don't actually want to disambiguate these, we're instead looking at pure textual offsets. The major change here was simplifying the code that handles selection on nodes with no children (cf, <hr>, <img>) and nodes that are outside the text selection component.
…have lost the original DOM tree / selection
…(deletion/update of annotations TK)
…th local failures
} | ||
|
||
onSave(evt: Event) { | ||
let textColor = this.shadowRoot.querySelector('.text-color'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blaine Should this be grabbing the corresponding attribute instead of querying for the element?
this.getAttribute('text-color')
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The color picker is pretty primitive, so it uses <input type=color>
and this is just getting the element to propagate it up, using element.value
to fetch the actual color value.
@@ -6,7 +6,7 @@ | |||
"module": "dist/modules/index.js", | |||
"types": "dist/commonjs/index.d.ts", | |||
"scripts": { | |||
"build": "rm -rf dist; tsc -p . && tsc -p . --module ESNext --outDir dist/modules/ --target ES2017", | |||
"build": "rm -rf dist; tsc -p . ; tsc -p . --module ESNext --outDir dist/modules/ --target ES2017; exit 0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment is about updating "@atjson/document": "0.8.4"
to 0.8.5
@@ -6,7 +6,7 @@ | |||
"module": "dist/modules/index.js", | |||
"types": "dist/commonjs/index.d.ts", | |||
"scripts": { | |||
"build": "rm -rf dist; tsc -p . && tsc -p . --module ESNext --outDir dist/modules/ --target ES2017", | |||
"build": "rm -rf dist; tsc -p . ; tsc -p . --module ESNext --outDir dist/modules/ --target ES2017; exit 0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment is about updating "@atjson/document": "0.8.4"
to 0.8.5
@blaine / @foobarrio this gist should help with a bunch of the TypeScript errors in the component: |
This sets a TypeScript compilation context for ts files in test/ allowing VSCode (among other editors) to surface TypeScript errors.
No description provided.