1 2 3 4 Previous Next 46 Replies Latest reply: Apr 12, 2014 9:53 AM by Dude! RSS

List of forum editor issues and bugs

Dude! Guru
Currently Being Moderated

This thread is work in progress. Please report additional bugs and issues you are aware off. I will try to reproduce the issue and add your information to the appropriate columns below. Thanks!

 

Note: For accurate results, the width of your web browser window needs to be adjusted to show the following dotted line as a single line. Your screen resolution needs to be at least 1280 pixels wide.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 

 

 

IssueDateSummaryBrowserPriorityStatusRemark
108-Jan-2014Text copied from discussions, such as code, result in double line spacing when copied to the host system.

Firefox 25.0

Internet Explorer 9

1open1
208-Jan-2014Cannot append text or code to Syntax Highlighting.Firefox 25.01open
308-Jan-2014Cannot properly select text or code with Syntax Highlighting.Firefox 25.01open
408-Jan-2014Subsequent edit sessions add empty lines to Syntax Highlighting code.Firefox 25.01open
508-Jan-2014Copying text under Syntax Highlighting includes line numbers.Safari 7.0.1
Chrome 31.0
1open5
608-Jan-2014Cannot copy and paste the whole Syntax Highlighting frame.Firefox 25.03open
709-Jan-2014Syntax Highlighting suppresses empty lines and white space when browsing.Firefox 25.02open
808-Jan-2014Syntax Highlighting overwrites font.any1open
909-Jan-2014Cannot paste any text into the editor window.Internet Explorer 111open
1009-Jan-2014Cannot change the font when selecting several lines of text.Firefox 252open
1109-Jan-2014Changing the font gets confused and shows the wrong font.Firefox 251open
1209-Jan-2014Pasting a URL captures the text insertion point.Firefox 251open
1316-Jan-2014Quoting captures insertion point.Firefox 251open
1424-Jan-2014Adding HTML label tag for no apparent reason.Firefox 251open

 

1528-Feb-2014Undo disables functions, such as Quote and Syntax Highlighting and results in complete loss of text when attempting to post.Firefox 261open
1628-Feb-2014Syntax Highlighting shows several <span> when browsing.Firefox 262open

 

 

 

Ref. No.Remarks
1The problem applies to any version of the named web browsers.
5Code without line numbers can be copied in Firefox when carefully selected without line numbers. Copying the code will insert line numbers when the selection includes line numbers, although they do not appear highlighted: http://img845.imageshack.us/img845/6145/bezs.jpg

 

 

 

IssueSteps to reproduceWorkaround
1

Copy a couple or more lines of text from a discussion window and paste it into any application or document on your host system. For instance:

 

The following may produce double line spacing:

If there are two or more ways to do something, and one of those

ways can result in a catastrophe, then someone will do it.

 

The following should work correctly:

If there is a possibility of several things going wrong, the one that will
cause the most damage will be the first one to go wrong

  • Use Shift-Return instead of Return to terminate the end of lines when creating text.
  • Use a different browser to perform cut and paste operations, such as Apple Safari or Google Chrome.
2

Paste some text code into the forum editor window. Select the code and choose Syntax Highlighting:Plain from the editor toolbar (>>). Close and re-edit the thread. It is not possible to place the insertion point below the block of code in order to add any additional lines of code or to add any normal text. For instance:

 

mknod compress_pipe p
mknod export_pipe p
chmod +rw export_pipe compress_pipe
nohup split -b 8192m < export_pipe &
nohup gzip < compress_pipe > export_pipe &
exp system/passwd full=y direct=y consistent=y compress=n \
buffer=10485760 file=compress_pipe








































  • It is possible to insert additional code or text below Syntax Highlighting, provided the frame it is not the end, as shown in issue 7.
  • Add any line of text at the end of your code before applying Syntax Highlighting to the lines above.
  • Adding code within the frame of Syntax Highlighting works in Safari and Google Chrome.
3

Re-edit a post with Syntax Highlighting. It is not possible to properly select any lines of code. An additional empty code line is added and the focus is shifted. The selection mask does not match the actual text. It is pretty much impossible to re-edit Syntax Highlighting.

Screenshot: http://img24.imageshack.us/img24/6121/viun.jpg

Use Safari or Google Chrome when to re-edit text or code under Syntax Highlighting.

4

Every subsequent edit of a post with Syntax Highlighting adds an empty blank line to the code block with an incremented line number. The resulting empty lines (07, 08) shown in the screenshot cannot be selected or removed unless there is text below the code frame as shown in issue 7. Screenshot: http://img809.imageshack.us/img809/5514/cxkd.jpg

Removing of empty lines woks in Safari and Google Chrome.

5When browsing code with Syntax Highlighting, it is not possible to select the code without the line numbers. Screenshot: http://img835.imageshack.us/img835/6626/j7n7.jpg

Select and copy each line separately. Or use Firefox or Google Chrome, but note issue in Remark 5.

6

When editing, it is possible to copy and paste lines under Syntax Highlighting when selecting the lines, but not when selecting the complete Syntax Highlighting frame.

Carefully select text without the Syntax Highlighting frame boundaries.

7

Empty lines and white space (identation) in Syntax Highlighting are suppressed when browsing, although they exist in the actual post. For instance:

 

mknod compress_pipe p
mknod export_pipe p





































 

Screenshot when editing the above code:

http://img401.imageshack.us/img401/673/kmy4.jpg

8

Syntax Highlighting changes the font to Arial and it is not possible to apply something more suitable for the displaying of code, such as fixed-width Courier New.

 

Arial: 1l0OI

Courier New: 1l0OI


Arial: 1l0OI
Courier New: 1l0OI



































9It is not possible to paste any text into the editor window.

Use a different web browser or downgrade to IE 10.

Or enable F12 Developer Tools from the Tools menu. Press Ctrl-8
Change the default document mode from Edge to IE 10. Select Leave this page.

10

Create a new thread and type several lines of text. Then select select several lines of text and choose a font, e.g. Courier New. Not all selected lines are changed and only a couple of lines remain highlighted. For instance:

 

It is difficult to prove the existence of aliens.

Photos exist with aliens, but they could be fake.

On the other hand, photos without aliens could be fake too.

11Select a line of text and change the font to Courier New. Then select the line again and it will show Arial. Change the font to Courier New and the text will change back to Arial.
12

Copy a URL and paste it into the editor window. The URL will be shown as a hyperlink using blue text. It is not possible to continue with normal writing without changing the text of the link. The text insertion point is captured inside the text of the link when trying to click below the link.

After pasting the URL, use the arrow key or mouse to move the cursor to the end of the link, then press RETURN and start writing normally. You can than move the cursor to the beginning of the line and use BACKSPACE to move the text up, after the link.

13When replying to a thread and pressing the Quote Previous Message button and then clicking inside the quoted text, for instance, to remove some of the content, it is sometimes no longer possible to move the text insertion point outside of the quoted text back to the normal editing area.When this happens it helps to switch to HTML and then switch back to the Full Editor.
14While writing normal text in the editor, it sometimes becomes impossible to edit a line of text. When clicking on any text to move the text insertion point, it selects the complete paragraph instead. http://imagizer.imageshack.us/v2/800x600q90/585/d0v5.jpg. When pressing the "Post Message" button, a dialog appears to "Stay" or "Leave" the page.Apparently the editor adds HTML label tags for no apparent reason, which can be seen when switching the editor to HTML mode. http://imagizer.imageshack.us/v2/800x600q90/199/1r5a.jpg
15Copy some text into the editor window. Select the text and choose Syntax Highlighting form the >> insert toolbar. Undo using Ctrl-z. It is no longer possible to use any of the >> insert functions. After that it is also not possible to post the message, resulting in an unexpected error and the content is lost.
16Syntax Highlighting shows several <span> at the beginning and end of the Syntax Highlighting block after posting. This affects old and new posts.
  • 1. Re: List of forum editor issues and bugs
    moniquevdb-oracle Guru Moderator
    Currently Being Moderated

    Holy.... wow, this is helpful, thank you so much for kicking this off, Dude!

     

    BluShadow I know you are in favor of reenabling code formatting and ditching the Syntax Highlighter altogether. I've also heard that users would prefer the advanced editor to open by default. Anything else on the wishlist?

  • 2. Re: List of forum editor issues and bugs
    Dude! Guru
    Currently Being Moderated

    Thanks, glad to help! There is still a lot left to do though.

     

    I think the advanced forum editor is really not that much advanced for anyone with a computer background. But my heartbeat increases when I have to switch to the advanced editor to reach for the “remove formatting” button. So If you ask me, please make the advanced editor the default.

     

    Regarding Syntax Highlighting, I prefer a button solution, which makes selected text appear similar to the previous forum when using the {code} tags. It made text appear in a fixed-width font and added a frame with a grey background and horizontal scroll bar when necessary to prevent automatic line wrapping. I do not want any line numbers to be added and no suppressing of empty lines or computer paper background. I would however like to be able to change the font style and color of individual text fragments.

  • 3. Re: List of forum editor issues and bugs
    BluShadow Guru Moderator
    Currently Being Moderated

    moniquevdb_oracle wrote:

     

    Holy.... wow, this is helpful, thank you so much for kicking this off, Dude!

     

    BluShadow I know you are in favor of reenabling code formatting and ditching the Syntax Highlighter altogether. I've also heard that users would prefer the advanced editor to open by default. Anything else on the wishlist?

     

    correction, I would certainly be in favour (favor to you ) of reenabling code tags, mainly because I work quicker by copy/paste and by keyboard than by having to click through a load of buttons (that currently don't do what they should).  I've not said that syntax highlighting should be ditched altogether, and I'd certainly be in favour of it being there, just so long as it provided a decent formatting that was appropriate, so code actually looked like code, and the ability for people to copy/paste the code out of the forum to their own environment wasn't corrupted with double line spacing (as dude has already mentioned) and the addition of the line numbers it puts in (the line numbers are useful for reference on the forum, e.g. when we want to say "you're problem is on line X", but not good when you copy/paste code out to your environment and have to spend ages deleting them all to get the code to do anything).  If it's too difficult, then removing the line numbers from the code formatting would be preferable to having them there and not being able to copy the code out without them.

    I agree with dude that it would be good to be able to highlight portions of code with bold or colours, which the old forum didn't allow, but this one does, so it's really a combination of old and new that's needed.  And as dude highlights, the supressing of blank lines is a pain as it can make the posting of multiple code commands become all compressed and difficult to read, and is not representative of what we have in our interfaces such as SQL*Plus etc.

     

    Basic example:


    Copy paste from my SQL*Plus window into the forum (and me applying courier new and quoting it)...

     

    SQL> select * from emp;

         EMPNO ENAME      JOB              MGR HIREDATE                    SAL       COMM     DEPTNO
    ---------- ---------- --------- ---------- -------------------- ---------- ---------- ----------
          7369 SMITH      CLERK           7902 17-DEC-1980 00:00:00        800                    20
          7499 ALLEN      SALESMAN        7698 20-FEB-1981 00:00:00       1600        300         30
          7521 WARD       SALESMAN        7698 22-FEB-1981 00:00:00       1250        500         30
          7566 JONES      MANAGER         7839 02-APR-1981 00:00:00       2975                    20
          7654 MARTIN     SALESMAN        7698 28-SEP-1981 00:00:00       1250       1400         30
          7698 BLAKE      MANAGER         7839 01-MAY-1981 00:00:00       2850                    30
          7782 CLARK      MANAGER         7839 09-JUN-1981 00:00:00       2450                    10
          7788 SCOTT      ANALYST         7566 19-APR-1987 00:00:00       3000                    20
          7839 KING       PRESIDENT            17-NOV-1981 00:00:00       5000                    10
          7844 TURNER     SALESMAN        7698 08-SEP-1981 00:00:00       1500          0         30
          7876 ADAMS      CLERK           7788 23-MAY-1987 00:00:00       1100                    20
          7900 JAMES      CLERK           7698 03-DEC-1981 00:00:00        950                    30
          7902 FORD       ANALYST         7566 03-DEC-1981 00:00:00       3000                    20
          7934 MILLER     CLERK           7782 23-JAN-1982 00:00:00       1300                    10

    14 rows selected.

    SQL> select * from dept;

        DEPTNO DNAME          LOC
    ---------- -------------- -------------
            10 ACCOUNTING     NEW YORK
            20 RESEARCH       DALLAS
            30 SALES          CHICAGO
            40 OPERATIONS     BOSTON

    SQL>


    but in my SQL*Plus window it looks like.

     

    SQL> select * from emp;

     

         EMPNO ENAME      JOB              MGR HIREDATE                    SAL       COMM     DEPTNO
    ---------- ---------- --------- ---------- -------------------- ---------- ---------- ----------
          7369 SMITH      CLERK           7902 17-DEC-1980 00:00:00        800                    20
          7499 ALLEN      SALESMAN        7698 20-FEB-1981 00:00:00       1600        300         30
          7521 WARD       SALESMAN        7698 22-FEB-1981 00:00:00       1250        500         30
          7566 JONES      MANAGER         7839 02-APR-1981 00:00:00       2975                    20
          7654 MARTIN     SALESMAN        7698 28-SEP-1981 00:00:00       1250       1400         30
          7698 BLAKE      MANAGER         7839 01-MAY-1981 00:00:00       2850                    30
          7782 CLARK      MANAGER         7839 09-JUN-1981 00:00:00       2450                    10
          7788 SCOTT      ANALYST         7566 19-APR-1987 00:00:00       3000                    20
          7839 KING       PRESIDENT            17-NOV-1981 00:00:00       5000                    10
          7844 TURNER     SALESMAN        7698 08-SEP-1981 00:00:00       1500          0         30
          7876 ADAMS      CLERK           7788 23-MAY-1987 00:00:00       1100                    20
          7900 JAMES      CLERK           7698 03-DEC-1981 00:00:00        950                    30
          7902 FORD       ANALYST         7566 03-DEC-1981 00:00:00       3000                    20
          7934 MILLER     CLERK           7782 23-JAN-1982 00:00:00       1300                    10

     

    14 rows selected.

     

    SQL> select * from dept;

     

        DEPTNO DNAME          LOC
    ---------- -------------- -------------
            10 ACCOUNTING     NEW YORK
            20 RESEARCH       DALLAS
            30 SALES          CHICAGO
            40 OPERATIONS     BOSTON

     

    SQL>


    Obviously that's a basic example; in reality we can be providing a solution to someone, explaining multiple steps and commands to demonstrate their issue and the solution, and having to go back through the code once we've pasted it adding back in all the line spacings, is a real pain and time consuming.

     

    Certainly, having the advanced editor options available immediately for replying would be better than having to switch to it manually, especially as most people using these forums are going to want to paste code in (what with it being a technical forum and not really a social forum), and the basic editor just doesn't allow for any suitable code formatting (unless the person is mad enough to switch to HTML mode).

  • 4. Re: List of forum editor issues and bugs
    Christian Erlinger Guru
    Currently Being Moderated

    I would certainly be in favour (favor to you ) of reenabling code tags, mainly because I work quicker by copy/paste and by keyboard than by having to click through a load of buttons (that currently don't do what they should).

    +1. I really miss the [code] (or {code}) tags.

     

    Just a wish for the syntax highlighting (I understand if it isn't possible at all): it might be plagiarism, but the code plugin of dokuwiki allows to set the used syntax highlighting in the code tag as well like:

     

    <code plsql>

    some_plsql_code;

    </code>

    or

    <code cpp>

    some_cplusplus_code;

    </code>

     

    maybe something like that could prove useful to the non-WYSIWYG editor zealots like me?

     

    cheers

  • 5. Re: List of forum editor issues and bugs
    Dude! Guru
    Currently Being Moderated

    Code must also not be wrapped and may need a horizontal scroll bar depending on the width of the browser window. It should also allow any character and should not call special internal functions when running into @ and # signs.

     

     

    The tags used in the previous forum actually made it difficult to maintain useful copies for my own archive. So I usually ended up editing two versions of one and the same document: a forum version and a local copy. I was happy to see that the new forum uses HTML and is WYSIWIG, so I thought I could standardize on HTML. In practice however, copying HTML between the forum and any other editor produces unpredictable results because the forum editor is stripping and converting HTML.

     

     

    Whether to type {code} tags or selecting text and pushing a button does not really make a different to me. Typing {code} tags as opposed to pushing a button may conflict with the WYSIWIG feature of the editor. I doubt that you can have both options at the same time.

     

     

    Btw, speaking of WYSIWG, what you edit is not necessarily what you get because the discussion browser is about 1/3 smaller than the editor window due to the action items shown at the right hand side. This means there is going to be automatic wrapping of text, which is bad for tables and code.

  • 6. Re: List of forum editor issues and bugs
    BluShadow Guru Moderator
    Currently Being Moderated

    Dude! wrote:

      

    Whether to type {code} tags or selecting text and pushing a button does not really make a different to me. Typing {code} tags as opposed to pushing a button may conflict with the WYSIWIG feature of the editor. I doubt that you can have both options at the same time.

     

     

    No reason you can't have both options.  After all the editor seems quite happy to convert : ) into as you type. 

  • 7. Re: List of forum editor issues and bugs
    jgarry Guru
    Currently Being Moderated

    BluShadow wrote:

     

     

    Certainly, having the advanced editor options available immediately for replying would be better than having to switch to it manually, especially as most people using these forums are going to want to paste code in (what with it being a technical forum and not really a social forum), and the basic editor just doesn't allow for any suitable code formatting (unless the person is mad enough to switch to HTML mode).

    It looks to me like switching into the advanced editor is actually doing some HTML pre-processing (that window that appears on the left with a bunch of HTML code, before it presents the post in the editor).  Perhaps that is the source of all the problems.

     

    I'd like to have the advanced editor options available immediately too, just not an editor this "advanced."  (Now humming "Jocko Homo.")

  • 8. Re: List of forum editor issues and bugs
    Dude! Guru
    Currently Being Moderated

    Well, I don't know, but I think catching keystrokes like , which gets converted right away might be different than more complex processing using {code} tags. Text between {code} tags will probably need to be converted to some html when submitting, then how can the editor rebuild the content using the original {code} tags when re-editing? Anyway, I would leave it up to the developer to think about it. Either way, button or tag is fine with me.

  • 9. Re: List of forum editor issues and bugs
    moniquevdb-oracle Guru Moderator
    Currently Being Moderated

    Thanks, this makes sense. Keep the ideas coming in this thread and in the meantime I will keep working on it from my end and see what we can do.

  • 10. Re: List of forum editor issues and bugs
    Dude! Guru
    Currently Being Moderated

    I think I'm pretty much done covering the issues I have run into without doing anything fancy or advanced. If anybody can add something to the list, please reply.

     

    I'm not sure if it makes sense to continue to test the results in different browsers, because I think the editor should work with all common browsers and recent versions worth mentioning.

  • 11. Re: List of forum editor issues and bugs
    BluShadow Guru Moderator
    Currently Being Moderated

    Dude! wrote:

     

    I think I'm pretty much done covering the issues I have run into without doing anything fancy or advanced. If anybody can add something to the list, please reply.

     

    I'm not sure if it makes sense to continue to test the results in different browsers, because I think the editor should work with all common browsers and recent versions worth mentioning.

    Yeah, a lot of the issues you've posted for Firefox I see in Internet Explorer 9.

    I think it's just a case of indicating what issues have been found, and that those issues have are reproduced in one of the 'standard' web browsers.

  • 12. Re: List of forum editor issues and bugs
    Dude! Guru
    Currently Being Moderated

    Let's hope the crosslinking of this thread has been fixed for good now.

  • 13. Re: List of forum editor issues and bugs
    scott.wesley Guru
    Currently Being Moderated

    +1 for improving syntax highlighting process. It's fundamental to the operation of the site and should be made as simple as can be to apply, but options available.

     

    I'm in favour of bringing back the {code} option, but also having a one click icon to apply the same formatting via the default menu.

     

    Monospace characters is a must, but perhaps allow for varation in formatting with tags like {sql}  {css}  ?

  • 14. Re: List of forum editor issues and bugs
    Dude! Guru
    Currently Being Moderated

    For what it's worth, I just added No. 13.

1 2 3 4 Previous Next