Testing new forum code ...

Phil Pilgrim (PhiPi) · 2018-10-02 19:11

Does ^superscript work now?
How about _subscript?
And [noparse]noparse[/noparse]?

Nope, nope, and nope. Still waiting and hoping ...

-Phil

jmg · 2018-10-02 19:14

Phil Pilgrim (PhiPi) wrote: »

Does ^superscript work now?
How about _subscript?
And [noparse]noparse[/noparse]?

Nope, nope, and nope. Still waiting and hoping ...

-Phil

Here the first two appear to do something ?

Testing: 8) or 8 ) still flips to an icon...

Phil Pilgrim (PhiPi) · 2018-10-02 19:19

jmg wrote:

Here the first two appear to do something ?

Not on my MacBook with Chrome, although the BBCodes disappear. I'll try on a PC ...

Just looked at the page source, and and are both there. So those two have been added. Yay!

-Phil

jmg · 2018-10-02 20:32

Phil Pilgrim (PhiPi) wrote: »

jmg wrote:

Here the first two appear to do something ?

Not on my MacBook with Chrome, although the BBCodes disappear. I'll try on a PC ...

Just looked at the page source, and and are both there. So those two have been added. Yay!

Hmm, changed from IPad and Safari, which worked, to PC and Chrome, and the rendering and fails.... - looks like Chrome users cannot see this ?

ozpropdev · 2018-10-02 22:38

First two work Ok here on Win10

DavidZemon · 2018-10-02 23:37

No super/sub working on my Android + Chrome or Ubuntu + Chrome

Hal Albach · 2018-10-02 23:52

Win 10 + Chrome and I see Phil's first post just fine - superscript up half a line and subscript down half a line, both in a smaller font. Going to see if it works with Edge........Yup, works on Edge, too.

Hal Albach · 2018-10-02 23:54

Has anyone noticed if unread messages randomly pop up as read when returning from a thread?

jmg · 2018-10-02 23:55

Hal Albach wrote: »

Win 10 + Chrome and I see Phil's first post just fine - superscript up half a line and subscript down half a line, both in a smaller font. Going to see if it works with Edge........Yup, works on Edge, too.

Hmm, maybe the version matters ?
I have Win10, updated a few nights ago, and
Google Chrome is up to date
Version 69.0.3497.100 (Official Build) (64-bit)

that fails to render right, but I did see it ok on iPad/Safari

Hal Albach · 2018-10-02 23:58

I just did a Win 10 update today and Chrome is at Version 69.0.3497.100 (Official Build) (64-bit) also.

Phil Pilgrim (PhiPi) · 2018-10-03 00:01

Both sub and sup work with Firefox and Chrome on Win7. I also dug into the CSS files to see if maybe there was some weirdness with vertical-align that might confuse some browsers, but they're correctly defined for the userContent section. So I have to assume it's a browser issue.

Would really like to have noparse working, though ...

-Phil

Hal Albach · 2018-10-03 00:02

My Win specs are:
Win 10 Pro
ver 1803
OS Build 17134.320

Heater. · 2018-10-03 00:03

That's odd, Win 10 here and:

Chrome 69.0.3497.100 - Nope, nope and nope. Superscript, subscript and noparse does not work.

Firefox 61 - Yep, yep and nope. Super and subscript work, noparse does not.

Edge - Same as Firefox.

I notice some changes to the way code blocks are displayed. There seems to be some syntax highlighting going on. Except it's a total mess. For Spin code at least.

1) Happy.
2) Happy.
3) Happy.
4) Happy.
5) Happy.
6) Happy.
7) Happy.
8) Sad.
9) Happy.

evanh · 2018-10-03 00:10

The real test for parsing is in code blocks:

8)

evanh · 2018-10-03 00:12

Yay! 8)

evanh · 2018-10-03 00:16

There's an intermittent problem with posting refresh getting stuck. The post is successfully made ... the page goes blank and the browser sits waiting for the forum to refresh but nothing happens and the browser times out.

A manual reload of the forum shows a new posting - the one just posted.

EDIT: Sometimes the page doesn't even go blank. It just hangs like the posting wasn't made at all. But it still is posted.

PS: This is all without scripting so those with scripting enabled might experience it differently.

Heater. · 2018-10-03 00:20

Boo! 8)

Phil Pilgrim (PhiPi) · 2018-10-03 00:23

evanh wrote:

There's an intermittent problem with posting refresh getting stuck. ...

I've noticed that, too. Moreover, if I preview a new post, I'm unable to reedit it, since the Edit button is grayed out.

-Phil

evanh · 2018-10-03 00:24

[deleted]

Heater. · 2018-10-03 00:25

PUB weirdSyntaxHighlighting : x, y, z
    while z == 0
        x := 42
        ' What is this ?
        y := x
    return 10000

evanh · 2018-10-03 00:26

Heater,
The highlighting/colouring only appears with scripting enabled.

Dave Hein · 2018-10-03 00:38

Testing at-at-var.
@@var

@@var

Doesn't work. One of the @'s disappears.

Testing at-var.
@var

@var

That works, except when I type @var it tries to autocomplete with something from it's dictionary. If I put a space after @var it leaves it as I type it, but if I hit a CR it autocompletes with @varnon .
Maybe it's a browser thing. I'm using Edge.

Heater. · 2018-10-03 00:41

I always have scripting enabled. I have coloring. It's a mess.

Here is a longer example:

PUB AddNums(Num1,Num2):Flag
    Num1_ := Num1
    Num2_ := Num2
    cognew(@entry, @Num1)

    'waitcnt(cnt+10000)
    'return Flag
   
    repeat while Flag == 0

    return Num1

DAT
                        org
entry
                        mov     t1,   par       ' Move argument address into t1
                        add     t1,   #8        ' Point to 3rd argument ( In this case 'Flag' )
                       
                        wrlong  Zero, t1        ' Clear 'Flag before we start'
                        
                        add     Num1_,Num2_     ' Add Num1 to Num2
                        wrlong  Num1_, par      ' Return result to Num1

                        wrlong  One, t1         ' Set 'Flag when we are done'

                        CogId   CogNum          ' Get COG ID
                        CogStop CogNum          ' Stop this COG

CogNum                  long    0               ' Reserved variables
Num1_                   long    0
Num2_                   long    0

Zero                    long    0
One                     long    1

t1                      res     1

evanh · 2018-10-03 00:43

Bugger. We need our @s. I've never understood the enthusiasm for doing that to a person's name in the first place.

evanh · 2018-10-03 00:47

Dave Hein wrote: »

...but if I hit a CR it autocompletes with @varnon .
Maybe it's a browser thing. I'm using Edge.

It'll be a scripting thing.

Tor · 2018-10-04 10:58

I dislike how the new update shows every second post with a coloured background. My brain thinks "quote" automatically, whatever I do. I don't like this change.

(Why is this thread sunk, by the way? It doesn't show up as having new posts)
(Edit: Although that post got it to the top.. however, yesterday's posts didn't. Strange.)

Courtney Jacobs · 2018-10-04 13:35

This thread has not been sunk.

Wuerfel_21 · 2018-10-04 13:40

Slightly related: The forum does not auto-upgrade connections to HTTPS where possible. I really appreciate sites leaving the unencrypted connection available (some older/simpler browsers don't understand the new encryption protocols or have really outdated root certificates), but on a site where one has to enter a password, not using HTTPS is a really terrible idea.