I have to break "muscle memory" on this website since everyplace else works the way you expect it to.
Hm, I had a quick look around and at least Firefox handles other text entry fields (on other websites) differently, showing all edit options you'd expect. That hints at the editor being at fault here, presumably by not presenting itself to the browser as it should (some attribute wrong/missing?). At least something that justifies investigating, albeit with rather low prio.
Update: indeed, it's using a full-blown iframe instead of a textarea, yet the iframe's body is explicitly marked as contenteditable. Go figure...
Update 2: it works! You "just" need to do the right click on the editable area of the editor's content pane. That is, if it's still empty it means you have to hit the first line, but pay attention to the small gap at the top. Turns out you don't have to break your muscle memory but get a "chance to exercise it" ;-)
taking you to the top of the wrong page completely
additionally, it seems the page enumeration is a 0-n scale rather than 1-n. which makes comparing actual page number that you're on and what the hyperlink shows a little disingenuous. ie on page 27, the hyperlink indicates page 26.
Please note that the page numbers are irrelevant as everybody can set up their preferred number of posts per page. I do agree with you that your first link does not take you to the post number 177563. And neither does the two other links you provided (at least not for me, I have set 30 posts per page).
The first link does indeed take me to comment 177563, as expected. The actual page depends on the comments per pagepreference you set. Note that the link takes me to the correct comment regardless of the setting I use (tested 10 and 30).
The second and third links are only useful for yourself only, as their "meaning" depends on the individual comment per page setting. That's exactly why these "goto" links exist.
The 0-indexed page numbers are a known "issue" but they are irrelevant because of the above (they have no universal meaning anyway, they are internal/technical only).
In the cases the first link does not work for you: are you logged in at that moment? Also, you wrote "in some cases". Can you distinguish them somehow?
Keith Myers wrote:I have to
)
Hm, I had a quick look around and at least Firefox handles other text entry fields (on other websites) differently, showing all edit options you'd expect. That hints at the editor being at fault here, presumably by not presenting itself to the browser as it should (some attribute wrong/missing?). At least something that justifies investigating, albeit with rather low prio.
Update: indeed, it's using a full-blown iframe instead of a textarea, yet the iframe's body is explicitly marked as contenteditable. Go figure...
Update 2: it works! You "just" need to do the right click on the editable area of the editor's content pane. That is, if it's still empty it means you have to hit the first line, but pay attention to the small gap at the top. Turns out you don't have to break your muscle memory but get a "chance to exercise it" ;-)
Cheers,
Oliver
Einstein@Home Project
Thanks for the tip
)
Thanks for the tip Oliver. this is a test. It works as you state.
Hallo! I´m missing colored
)
Hallo!
I´m missing colored letters.
Kind regards and happy crunching
Martin
Are you...? ;-) Hang in
)
Are you...? ;-) Hang in there...
Einstein@Home Project
Colors work for
)
Colors work for me:
red
blue
yellow
green
orange
cyan as word
cyan as #00ffff
Ideas are not fixed, nor should they be; we live in model-dependent reality.
Yep, via BBCode but we might
)
Yep, via BBCode but we might also add it a more convenient way (toolbar button) down the line.
Thanks for the reminder
Einstein@Home Project
hyperlinks to specific
)
hyperlinks to specific messages seem to not work in some cases.
example:
a direct link to one of my comments (given by the "Message #" link) = https://einsteinathome.org/goto/comment/177563
which really exists as the second comment here: https://einsteinathome.org/content/discussion-thread-continuous-gw-search-known-o2md1-now-o2mdf-gpus-only?page=26
but the link takes you here: https://einsteinathome.org/content/discussion-thread-continuous-gw-search-known-o2md1-now-o2mdf-gpus-only?page=28#comment-177563
taking you to the top of the wrong page completely
additionally, it seems the page enumeration is a 0-n scale rather than 1-n. which makes comparing actual page number that you're on and what the hyperlink shows a little disingenuous. ie on page 27, the hyperlink indicates page 26.
_________________________________________________________________________
Please note that the page
)
Please note that the page numbers are irrelevant as everybody can set up their preferred number of posts per page. I do agree with you that your first link does not take you to the post number 177563. And neither does the two other links you provided (at least not for me, I have set 30 posts per page).
Hm, sorry, I can't reproduce
)
Hm, sorry, I can't reproduce that:
In the cases the first link does not work for you: are you logged in at that moment? Also, you wrote "in some cases". Can you distinguish them somehow?
Oliver
Einstein@Home Project
@Oliver Your link takes me
)
@Oliver
Your link takes me to post 177802 (or more likely to the top of page 19 [as shown at the bottom of the page]) and when I get there the address has transformed to: https://einsteinathome.org/content/discussion-thread-continuous-gw-search-known-o2md1-now-o2mdf-gpus-only?page=18#comment-177563 . I am using Chrome on win 7.