@davehawley
Yes, but honestly, why should I have to?!
What you type should be what you get. It is on every single other forum I use except this one.

Not at all.
Every decent forum has its ways to format text and do other stuff. How on earth should it be supposed to be not using certain reserved symbols??
There are regular characters - that which are used in ''normal'' language typing, right? Letters and punctuation marks. Agreed some of the latter are reserved here too, as well as ''not normal'' characters - like asterisc etc. But still.
Seriously???

Agreed that there's certain duplicating using both underscores and asteriscs for the same. However, it follows HTML standard - it's THERE where there is such duplicacy: they have their "strong" and other "schmong" which usually do exactly the same things - but they ''THINK'' they're reserving those in case some day in the future blah-blah-blah or some other schiit.

I wonder who's the most appropriate person in Opera, which can provide more details on that matter? - unless, there's already someone working on it, and this will be resolved any time soon?

Hi @joshl, thanks for the reply, yes, as Steve mentioned above, the old images are fine, but it seems, that the issue has a place, when one want to add some new images (in my case specifically PNG images).

No matter which type of image you try to attach: PNG, or JPG, it doesn't show up, and instead of it, it shows the link to the image.

It also doesn't matter, if one use the Markdown syntax, as shown below:

![Alt text](/path/to/img.jpg) or ![Alt text](/path/to/img.jpg "Optional title")

or that you use HTML tag:
![](path/to/image.jpg)

It just doesn't work. Is that know issue, and are you trying to fix it already, or not?

Have you tried opera://flags#enable-autofill-ignore-autocomplete-off?

The forum does not recognize opera:// urls...

Yeah, just tried this <link> syntax, so decided to move to a dedicated thread in order to undertake some experimenting...

First, what about trying to force it using Markdown?
Check 1: "opera://flags#enable-autofill-ignore-autocomplete-off" (a [link](link) syntax).
Now using HTML syntax: opera://flags#enable-autofill-ignore-autocomplete-off

Well, it doesn't seem to work: I can see a "denied-blah-blah" tooltip in both cases...
[WHISPER]It wasn't actually a tooltip, but you get it, I believe...:zip:[/WHISPER]
WHISPER2: Ah! Sorry! Forgot to mention I'm with Google Chrome now.///

Yes, apart from the Markdown syntax, you can format your input with most of basic HTML tags - inline ones mostly.

• Use starting the line with four whitespaces to show some code.
• Remember: Markdown syntax might sometimes not work within your HTML tags (or maybe otherwise**).

And yes, you're welcome to test some formatting in this thread.
But please, you might want to read it through first - lots of stuff has already been discussed and tested here previously.

Thanks*:)*

<p>The <dfn title="World Health Organization">WHO</dfn> was founded in 1948.
:rolleyes:
Yeah, it does! :yes:

@birdblack:
Hey, Birdblack, what do you think.. *_blah-blah-blah_* ...

Well, both ways - the italics thing works.

Yes the HTML tags that worked before all still work. In addition <em> now works as well. However, using the Markdown methods is quicker and easier, IMHO.

you don't need to "@poop" me that way

Ah yes, you did specifically ask me not to do that in this thread. Sorry!

Ok, emphasis works now and...

Well, does it?
And what about this?

Well, both ways - the italics thing works.
(Ruario, you don't need to "@poop" me that way: in any case I prefer the standard punctuation - like "Ruario, you don't need to...":cheers:)

Ok, emphasis works now and we have changed the help page to have [basic Markdown] instructions…

We also link them from the note below the comments input field. Hope that helps everyone.

In fact, putting extra lines before and after major elements sections (lists, quotes, blocks of pre-formatted text, line rules, etc.) is always a good idea.

You know what?
In most cases it might even look tidier - so you're generally right...

You can even put multiple if you like, they will not show as extras.

If I don't want to use line rules ("<hr>" or alike) but do want to show some (logical) separation within my posting, I insert between a double-break before and another one after*:idea:*

Four spaces ("sub"lines) within a list don't seem to make any difference to the output.

This is entirely as expected since Markdown and (HTML for that matter) cuts all whitespace (spaces, tabs and line breaks) down to a single space, unless marked up otherwise.

By the way, after a "---" line you don't need a spare line to get a <hr> output.

You might not need to (right now) but you should. Doing so is according to spec and should therefore prevent future problems if we update or change our Markdown parser. I even suggested this in Formatting with Markdown under "Quick summary" → "Avoiding common problems".

• Add a blank line before and after paragraphs, lists, quotes or blocks of preformatted text.

In fact, putting extra lines before and after major elements sections (lists, quotes, blocks of pre-formatted text, line rules, etc.) is always a good idea. You can even put multiple if you like, they will not show as extras. It is better to be liberal with blank lines, unless you are working with lists.

• Pets:
  dogs
  cats
  hamsters

• Wild animals:
  lions
  tigers
  bears

Yup. (By the way, after a "---" line you don't need a spare line to get a <hr> output.)
Now let me try another way:

• Pets:
  dogs
  cats
  hamsters

• Wild animals:
  lions
  tigers
  bears

Four spaces ("sub"lines) within a list don't seem to make any difference to the output.

…lists with paragraphs are broken.

Actually it seems you can do lists with paragraphs using two spaces at the end of the line to force a line break within the list, for example, this:

* **Pets:**  
  dogs  
  cats  
  hamsters
* **Wild animals:**  
  lions  
  tigers  
  bears

(Note: I have 2 spaces after "**Pets:**", "dogs", "cats", "**Wild animals:**", "lions" and "tigers").

That will display as:

• Pets:
  dogs
  cats
  hamsters
• Wild animals:
  lions
  tigers
  bears

I don't think you should have to do this if you follow the Markdown syntax page literally but it seems to be required with our implementation and at least provides a work around.

and this'll be your homework

Umm, OK.

You know what? Instead, I think I'll just skip responding to this thread or to you. Have fun with the formatting, I'm out.