#caret — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #caret, aggregated by home.social.
-
> "They were so aggressive in their text!"
< "Why, what'd they do?"
> "They used an ellipsis!"
Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]
#aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk
[1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".
-
> "They were so aggressive in their text!"
< "Why, what'd they do?"
> "They used an ellipsis!"
Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]
#aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk
[1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".
-
> "They were so aggressive in their text!"
< "Why, what'd they do?"
> "They used an ellipsis!"
Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]
#aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk
[1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".
-
> "They were so aggressive in their text!"
< "Why, what'd they do?"
> "They used an ellipsis!"
Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]
#aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk
[1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".
-
> "They were so aggressive in their text!"
< "Why, what'd they do?"
> "They used an ellipsis!"
Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]
#aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk
[1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".
-
In Safari, tabbing to a non-editable element destroys the current selection range.
That's bad enough, but get this -- the reset has *already happened* when the `focus` event fires, so we can't snapshot the data because it's already lost. And yet the resulting `selectionchange` event **hasn't** fired yet, so we can't use that event to filter-out the change.
Are you fucking kidding me??
-
In Safari, tabbing to a non-editable element destroys the current selection range.
That's bad enough, but get this -- the reset has *already happened* when the `focus` event fires, so we can't snapshot the data because it's already lost. And yet the resulting `selectionchange` event **hasn't** fired yet, so we can't use that event to filter-out the change.
Are you fucking kidding me??
-
In Safari, tabbing to a non-editable element destroys the current selection range.
That's bad enough, but get this -- the reset has *already happened* when the `focus` event fires, so we can't snapshot the data because it's already lost. And yet the resulting `selectionchange` event **hasn't** fired yet, so we can't use that event to filter-out the change.
Are you fucking kidding me??
-
In Safari, tabbing to a non-editable element destroys the current selection range.
That's bad enough, but get this -- the reset has *already happened* when the `focus` event fires, so we can't snapshot the data because it's already lost. And yet the resulting `selectionchange` event **hasn't** fired yet, so we can't use that event to filter-out the change.
Are you fucking kidding me??
-
In Safari, tabbing to a non-editable element destroys the current selection range.
That's bad enough, but get this -- the reset has *already happened* when the `focus` event fires, so we can't snapshot the data because it's already lost. And yet the resulting `selectionchange` event **hasn't** fired yet, so we can't use that event to filter-out the change.
Are you fucking kidding me??
-
Writing #javascript to handle #caret browsing is interesting.
Since `keydown` only fires for targets that can be `activeElement`, the event target from caret navigating plain text is always <body>.
However you can identify which element contains the caret, by evaluating the range data, which you can also do from `selectionchange` events.
And get this -- Safari still fires those events, even though it doesn't support caret browsing ... because it actually does, it just doesn't show the caret!
-
Writing #javascript to handle #caret browsing is interesting.
Since `keydown` only fires for targets that can be `activeElement`, the event target from caret navigating plain text is always <body>.
However you can identify which element contains the caret, by evaluating the range data, which you can also do from `selectionchange` events.
And get this -- Safari still fires those events, even though it doesn't support caret browsing ... because it actually does, it just doesn't show the caret!
-
Writing #javascript to handle #caret browsing is interesting.
Since `keydown` only fires for targets that can be `activeElement`, the event target from caret navigating plain text is always <body>.
However you can identify which element contains the caret, by evaluating the range data, which you can also do from `selectionchange` events.
And get this -- Safari still fires those events, even though it doesn't support caret browsing ... because it actually does, it just doesn't show the caret!
-
Writing #javascript to handle #caret browsing is interesting.
Since `keydown` only fires for targets that can be `activeElement`, the event target from caret navigating plain text is always <body>.
However you can identify which element contains the caret, by evaluating the range data, which you can also do from `selectionchange` events.
And get this -- Safari still fires those events, even though it doesn't support caret browsing ... because it actually does, it just doesn't show the caret!
-
Writing #javascript to handle #caret browsing is interesting.
Since `keydown` only fires for targets that can be `activeElement`, the event target from caret navigating plain text is always <body>.
However you can identify which element contains the caret, by evaluating the range data, which you can also do from `selectionchange` events.
And get this -- Safari still fires those events, even though it doesn't support caret browsing ... because it actually does, it just doesn't show the caret!
-
#Markdown Tips
Do you know the Markdown syntax for simple math symbols such as superscript and subscript in #iAWriter and #iAPresenter?
Our Markdown Guide has you covered: https://ia.net/writer/support/basics/markdown-guide#math
-
#Markdown Tips
Do you know the Markdown syntax for simple math symbols such as superscript and subscript in #iAWriter and #iAPresenter?
Our Markdown Guide has you covered: https://ia.net/writer/support/basics/markdown-guide#math
-
#Markdown Tips
Do you know the Markdown syntax for simple math symbols such as superscript and subscript in #iAWriter and #iAPresenter?
Our Markdown Guide has you covered: https://ia.net/writer/support/basics/markdown-guide#math
-
#Markdown Tips
Do you know the Markdown syntax for simple math symbols such as superscript and subscript in #iAWriter and #iAPresenter?
Our Markdown Guide has you covered: https://ia.net/writer/support/basics/markdown-guide#math
-
#Markdown Tips
Do you know the Markdown syntax for simple math symbols such as superscript and subscript in #iAWriter and #iAPresenter?
Our Markdown Guide has you covered: https://ia.net/writer/support/basics/markdown-guide#math
-
New PolicyViz Podcast episode with yours truly!
-
New PolicyViz Podcast episode with yours truly!
-
New PolicyViz Podcast episode with yours truly!
-
New PolicyViz Podcast episode with yours truly!
-
New PolicyViz Podcast episode with yours truly!
-
Worknote: Caret auf meinem Chromebook erkunden
Heute (und vermutlich auch in den nächsten Tagen) wird es auf diesen Seiten etwas ruhiger zugehen, denn ich habe mittlerweile mein Chromebook soweit getuned, daß ich es langsam produktiv einsetzen kann. Und diese Spielerei kostet natürlich Zeit, vor allem, da die Bedienung (vor allem, die vielen Sonderzeichen auf der Tastatur zu finden) noch etwas ungewohnt für mich ist. http://blog.schockwellenreiter.de/2022/07/2022072701.html #Caret #Chromebook #Texteditor #Webworking #Markdown
-
Worknote: Caret auf meinem Chromebook erkunden
Heute (und vermutlich auch in den nächsten Tagen) wird es auf diesen Seiten etwas ruhiger zugehen, denn ich habe mittlerweile mein Chromebook soweit getuned, daß ich es langsam produktiv einsetzen kann. Und diese Spielerei kostet natürlich Zeit, vor allem, da die Bedienung (vor allem, die vielen Sonderzeichen auf der Tastatur zu finden) noch etwas ungewohnt für mich ist. http://blog.schockwellenreiter.de/2022/07/2022072701.html #Caret #Chromebook #Texteditor #Webworking #Markdown
-
The Last Pimp: Der Caret Code Editor auf meinem Chromebook
image
Nach den Installationsorgien der letzten Tage, ein Teil fehlte mir noch, um mein Chromebook für mich wirklich nutzbar zu machen: Ein Texteditor, der ohne Ansehen der darunterliegenden Programmier- oder Auszeichungssprachen alles frißt, und dem es völlig egal ist, ob die Datei aus dem Linux-Unterbau meines Chromebooks, aus dem nativen Dateisystem oder aus Googles Cloud kommt. http://blog.schockwellenreiter.de/2022/07/2022072602.html #Caret #Texteditor #Chromebook -
The Last Pimp: Der Caret Code Editor auf meinem Chromebook
image
Nach den Installationsorgien der letzten Tage, ein Teil fehlte mir noch, um mein Chromebook für mich wirklich nutzbar zu machen: Ein Texteditor, der ohne Ansehen der darunterliegenden Programmier- oder Auszeichungssprachen alles frißt, und dem es völlig egal ist, ob die Datei aus dem Linux-Unterbau meines Chromebooks, aus dem nativen Dateisystem oder aus Googles Cloud kommt. http://blog.schockwellenreiter.de/2022/07/2022072602.html #Caret #Texteditor #Chromebook