<https://lh3.googleusercontent.com/-amf9s2yycDU/VyUSlSgNZoI/AAAAAAAAAM8/7YpwFvurX4g1eYiPCGLPfoJ959Hm-ae6gCLcB/s1600/screenshot-%257Bdomain%257D%2B%257Bdate%257D%2B%257Btime%257D.png>
cmari I concur on point (2)
<https://lh3.googleusercontent.com/-amf9s2yycDU/VyUSlSgNZoI/AAAAAAAAAM8/7YpwFvurX4g1eYiPCGLPfoJ959Hm-ae6gCLcB/s1600/screenshot-%257Bdomain%257D%2B%257Bdate%257D%2B%257Btime%257D.png>
<https://lh3.googleusercontent.com/-amf9s2yycDU/VyUSlSgNZoI/AAAAAAAAAM8/7YpwFvurX4g1eYiPCGLPfoJ959Hm-ae6gCLcB/s1600/screenshot-%257Bdomain%257D%2B%257Bdate%257D%2B%257Btime%257D.png>
cmari I concur on point (2)
On Saturday, 30 April 2016 20:34:41 UTC+2, cmari wrote:
>
> Note/questions from a non-expert (as illustrated by the fact that I'm
> going to have to wait for more clever people to demonstrate/document what
> can be done with sticky notes and list-children, because I have no clue!):
>
> 1. Undo/Redo behaves in a couple of unexpected (to me) ways in Chrome:
> - With the Preview pane open, both the undo and redo buttons have to be
> clicked twice in order to see the change reflected in the Preview pane.
> - Making this discovery caused me to notice that when I undo an extra time
> (past what was "done" to begin with, but necessary in order to undo in the
> preview pane), "undoundo" appears in the search bar.
>
> 2. I made an early transition to TW5 from twclassic precisely because
> apostrophes in tiddler titles seemed to be ok (great for people's names,
> book titles, etc), and I've never had any trouble with those titles in TW5.
> So I found the new warning a bit ominous and have two questions:
> - Has something really changed with this version, or is this fair warning
> about what has always been a risk?
> - Although the prerelease notes say "Added
> <https://github.com/Jermolene/TiddlyWiki5/issues/2351> a warning when
> *creating
> *tiddler titles containing troublesome characters", in fact, the warning
> shows up any time I edit an existing tiddler with an apostrophe in its
> title. Assuming my TW file is not going to blow up because of these already
> existing tiddlers, would it be possible to suppress the warning (save
> space) after the tiddler has been created?
>
> Although I don't tend to put a lot of content into tiddlers (hence my
> focus on titles), I really like the Editor Toolbar - the "link" lookup is
> going to be extremely useful - thanks!
> cmari
>
>
>
>
> On Saturday, April 30, 2016 at 6:43:23 AM UTC-7, Jeremy Ruston wrote:
>>
>> OK, after my disappointment recorded below, I came up with another
>> approach and I think have now got things working on Internet Explorer 11:
>>
>> http://tiddlywiki.com/prerelease
>>
>> It needs thoroughly testing under other browsers too, but seems to work
>> for me,
>>
>> Best wishes
>>
>> Jeremy.
>>
>> > On 30 Apr 2016, at 12:06, Jeremy Ruston <[email protected]> wrote:
>> >
>> > Hi Andrew
>> >
>> >> Now in IE 11, the whole edit field now clears if you change views and
>> also randomly. Something is wrong. It was working better. What changed?
>> >
>> > Nothing has changed in the code that updates the textarea. I think the
>> problem that we’re seeing in IE11 with the textarea display not being
>> updated is some kind of random bug.
>> >
>> > I’ve spent a few more hours investigating the problems with IE11 and
>> once again I’m out of ideas; I’ve been repeatedly finding the same outdated
>> information via searching Google, StackOverflow etc.
>> >
>> > The code in question is this part of framed.js:
>> >
>> > // Attempt to use a TextEvent to modify the value of
>> the control
>> > var textEvent =
>> this.domNode.ownerDocument.createEvent("TextEvent");
>> > if(textEvent.initTextEvent) {
>> > textEvent.initTextEvent("textInput", true,
>> true, null, operation.replacement, 9, "en-US");
>> > this.domNode.focus();
>> >
>>
>> this.domNode.setSelectionRange(operation.cutStart,operation.cutEnd);
>>
>> > this.domNode.dispatchEvent(textEvent);
>> > } else {
>> > this.domNode.value = newText;
>> > }
>> >
>> > IE11 has the initTextEvent method, and so calls the first code path.
>> The problem is that the value underlying the textarea is updated, but the
>> display is not updated to match.
>> >
>> > Best wishes
>> >
>> > Jeremy.
>> >
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups "TiddlyWiki" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> an email to [email protected].
>> >> To post to this group, send email to [email protected].
>> >> Visit this group at https://groups.google.com/group/tiddlywiki.
>> >> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/5b46be97-e9f8-4f99-ba1c-5b5b2ac3cbe1%40googlegroups.com.
>>
>>
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>>
>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/990621d6-1f92-400f-93b3-a5b1ae356328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
