I've created an issue for the problem:
https://github.com/TiddlyWiki/tiddlywiki/issues/118
Best wishes
Jeremy
On Tue, Feb 26, 2013 at 6:52 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:
Hi Tobias
Good catch, thank you very much for that. I'll explore a proper fix as
soon as I can,
Hi Tobias
Good catch, thank you very much for that. I'll explore a proper fix as soon
as I can,
Best wishes
Jeremy
On Sunday, 24 February 2013, Tobias Beer wrote:
Ho again Scott,
The problematic code seems to be this...
enclosedTextHelper: function(w) {
this.lookaheadRegExp.lastIndex =
Lookit you! I doubt it would ever have occurred to me to go looking for
something like that. I guess IE is abandoning \r in favor of \n — but why
on Earth no preserve backward-compability with their own parsing
preference? (Unless they've been preserving it for a couple of versions
already
On Friday, February 22, 2013 3:52:42 PM UTC-5, Tobias Beer wrote:
I just noticed something really funny...
1) Open the page in IE 10 desktop mode
2) Turn on the developer pane by hitting F12
3) click edit button in the HTML view toolbar
4) click it again withouth actually editing anything
Ho again Scott,
The problematic code seems to be this...
enclosedTextHelper: function(w) {
this.lookaheadRegExp.lastIndex = w.matchStart;
var lookaheadMatch = this.lookaheadRegExp.exec(w.source);
if(lookaheadMatch lookaheadMatch.index == w.matchStart) {
var text = lookaheadMatch[1];
*
Hi Scott Jeremy,
I just noticed something really funny...
1) Open the page in IE 10 desktop mode
2) Turn on the developer pane by hitting F12
3) click edit button in the HTML view toolbar
4) click it again withouth actually editing anything
5) now the linebreaks are displayed correctly
What's
By the way, Scott,
you probably already know... you can change the ie rendering mode to
another version also for local files within the developer tools; top-right
in the menu.
Cheers, Tobias.
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To
Thanks for the responses!
On Tuesday, February 19, 2013 7:08:05 AM UTC-5, Jeremy Ruston wrote:
visible difference between the two versions can be attributed to the HTTP
version being read only. Do you get the same behaviour if you visit your
site over HTTP with #readOnly:no at the end of the
Hi Scott
The different behaviour you're seeing when viewing over http vs. a file URI
is indeed very puzzling. Studying the screenshots, the other visible
difference between the two versions can be attributed to the HTTP version
being read only. Do you get the same behaviour if you visit your site
Thanks Tobias, good catch, patches much appreciated.
Best wishes
Jeremy
On Sat, Feb 16, 2013 at 6:21 PM, Tobias Beer beertob...@gmail.com wrote:
There is a bug in TiddlyWiki that may make it fail for ie10, e.g. the
ImageMacroPlugin, on which a few others depend on TiddlySpace: ieVersion
Hi Scott
I've had a quick look at your page in IE10, and am experiencing the same
missing line breaks problem, even though I'm viewing the page over HTTP.
I did find out that if you open the developer tools in IE with F10, and
then switch the Document Mode: Standards dropdown to IE9 mode, then
There is a bug in TiddlyWiki that may make it fail for ie10, e.g. the
ImageMacroPlugin, on which a few others depend on TiddlySpace: ieVersion
is not assessed correctly as it doesn't (yet) cater for any version 9 as
it only looks for a single digit. Was about to fork the master and and
Hi, Jeremy —
Sorry for disappearing for two weeks. I wanted to double-check on a
different machine and confirm that it stayed consistent — and then got
distracted by something shiny ... .
Here's what I can report:
- The display quirk occurs on at least one other Windows 8 machine
Hi Scott
I've not heard of this affecting TW on IE10. It sounds as though the CSS
for the pre element has been messed up to lose the white-space: pre
setting. Are you using any non-standard CSS?
Best wishes
Jeremy
On Mon, Jan 28, 2013 at 11:42 PM, Scott Simmons goo...@secret-hq.comwrote:
I've not heard of this affecting TW on IE10. It sounds as though the CSS
for the pre element has been messed up to lose the white-space: pre
setting. Are you using any non-standard CSS?
I HAVE been playing around with my StyleSheet lately, but I first noticed
this on a bare-bones TW that
I forgot to mention that it's not just IE10 that's new for my TWs; I'm also
editing them on Windows 8 for the first time.
--
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
Hi Scott
Just to be clear, do you get the problem when you view a tiddler on
tiddlywiki.com that contains monospaced formatting:
http://tiddlywiki.com/#ExamplePlugin
Or do you have to have editted the TiddlyWiki file on Windows 8 in order to
see the problem?
Best wishes
Jeremy
On Tue, Jan
I just started using IE10's engine to edit and save TWs and noticed that
hard returns inside long blocks of code set off by braces are ignored when
rendering tiddlers.
The effect is that
{{{
code
like this
block
}}}
is rendered as if it were
{{{
codelike thisblock
}}}
Anyone else noticed
18 matches
Mail list logo
