Tool 'Striket̶h̶r̶o̶u̶g̶h̶'

[chaot]

One of the problems with changing existing toolbars (on anything) is that some people 'know' the button they want by its position ... or its juxtaposition ...

Maybe something else is the problem. Hiding behind a view configured on the majority in order not to have to be active.
Fact is that this supposedly respected opinion is to a mass which swallows everything what you put in front of her.

One idle thought I had was to give the smileys panel a tabbed interface - Smileys and More Buttons

On the topic Smileys in MR I will open a new thread.

On a couple of phpBB boards I frequent, the bbcode for strikeout is [s]...[/s]

Mystery BBCode is on (bottom right) and still it doesn't work. (Maybe the Admin hasn't defined the code.)

How far we are I just do not know. Have lost sight. Thank you all for compliance!


I've been for years Chrome fan. Why? In plain terms: It works. Logical and beautiful. And that's just not the case in Firefox, it never was.

If we'd both would feel like it and had the time I could spend hours and hours to show us some kind of inconsistencies.

Add-on BBCodeXtra is installed. Compare the two images and decide what is wrong.

BBCodeXtra_Verfügbare Add-ons


BBCodeXtra_Meine Add-ons

I write a text and seek to cancel a text passage.
Lets say I want to strikeout seek to cancel and replace with want to strikeout.

Result should be like that:
I write a text and seek to cancel want to strikeout a text passage.

So I mark the passage seek to cancel and call with right click BBCodeXtra extension -> My Tags -> strikeout for to insert the code. What happens!? The illogical and unexpected happens: The marked passage just disappears.
I have first to call up the code and then paste in the intended text.

That's just crap!

But this Mozilla specialists always make a lot of wind, carry their noses high. Writing to these people is not much effectively as there is none or difficult to find a responsible. To see more public mailing lists.

And then they are not embarrassed to ask for a donation.

[eschwartz]

There is no default STRIKE tag in the FF extension, I wrote my own and it does not even mildly do what you accused it of doing. FYI it is defined as "[STRIKE]_selection_[/STRIKE]" (the _selection_ bit means it will surround selected text, rather than _clipboard_ which asks you to past it in, or nothing there, which will indeed replace the selection with the contents of the tag definition).

I have no idea what your pictures are supposed to mean, absent that "you installed it", so... congratulations?

Google chrome devs are no easier to get in touch with than Mozilla devs, but if you have a real problem and know what you are talking about I suspect either group will be responsive. Your complaints about the Mozilla devs specifically, indicate a subconscious bias.

There is absolutely no reason for them to be embarrassed about asking for donations. I am willing to bet they get thousands of cranks like you complaining about it every year, fortunately they also get enough donations from people who care enough to support their existence. It isn't exactly uncommon for open-source development teams to ask for donations.
Most of the software in the average person's computer relies heavily on or is offered for free. MANY of them would never exist in any significant way if they never received donations. Most/all have enriched everyone simply by existing, even if you don't use them -- case in point: Firefox pushed the web to its limits and jumpstarted the evolution of the modern browser.
You use a free product, it isn't unreasonable to be asked politely and in an unobtrusive way if you would like to support its future development.

Please stop confusing your confusion with how to use one unaffiliated extension, with fundamental problems in the development process of Mozilla itself, or whatever it is you seem to be upset about.

[BetterRed]

For the record I refuse to enter into browser wars, operating system wars, communication standards wars, video tape wars etc ... they are all so last century.

I'm an agnostic, iconoclast, card carrying member of the Official Monster Raving Loony Party and proud of it - and as of now an ignorer of this thread



BR

[eschwartz]

I generally don't care much either. But I will jump in to point out if someone is hating on a particular denomination for completely subjective reasons/illogic.

[DoctorOhh]

Originally Posted by eschwartz

"[STRIKE]_selection_[/STRIKE]" (the _selection_ bit means it will surround selected text, rather than _clipboard_ which asks you to past it in, or nothing there, which will indeed replace the selection with the contents of the tag definition).

Thank you for this example now my custom strike tag works as I hoped it would.

[chaot]

EDIT Posts overlapped. Refers to @eschwartz and @BetterRed

Generally you have're right to be angry.

Now I have changed the code from previously [strike][/strike] to [strike]_selection_[/strike] - and it works as expected.

Admittedly I had overlooked this available variables affair.
But I also assumed the habit in dealing with these tags that the default setting is to surround marked text if such exists. This is in MR and other forums I know the case.

I suspect that you are no longer interested in the following, but I mention it. The unfinished/unbalanced in Firefox which can always give rise to further conclusions (of production depth) we see (here) in the name of entry field:


Don't these devs see that!?

[DoctorOhh]

Originally Posted by chaot

I suspect that you are no longer interested in the following, but I mention it. The unfinished/unbalanced in Firefox which can always give rise to further conclusions (of production depth) we see (here) in the name of entry field:

Attachment 136139
Don't these devs see that!?

It looks like it is a translation bug. I don't see that bug. (see attached) I also don't see the little logo, what version are you running? I'm running 36.01.

[chaot]

I use German interface (in some things).
Name des Eintrags I translated freehand (and apparently inappropriate) with name of entry. Instead it is: Item name.

My concern in relation to the lack of production depth refers to the design of the input field (it's too long).

I use default Firefox version implemented in Linux Xubuntu 14.04 (LTS) - the version number I didn't find on the fly.

Which little logo you can't see?
Now I see what you mean (Firefox logo).



I don't know.

[eschwartz]

Originally Posted by DoctorOhh

Thank you for this example now my custom strike tag works as I hoped it would.

You're welcome.

[eschwartz]

Originally Posted by chaot

I use German interface (in some things).
Name des Eintrags I translated freehand (and apparently inappropriate) with name of entry. Instead it is: Item name.

My concern in relation to the lack of production depth refers to the design of the input field (it's too long).

I use default Firefox version implemented in Linux Xubuntu 14.04 (LTS) - the version number I didn't find on the fly.

Translation bug then -- third-party extensions and software without a multimillion-person userbase needs a little help getting foreign languages right -- everything defaults to English usually, and translations can be non-existent, based on automatic translations (incaccurate) or incomplete.

That cannot be strictly pleasant for people whose native language is not English -- yet it is something MOST projects have difficulty with.
It doesn't give anyone the right to jump to conclusions (a most unwise move, as a general rule of thumb).

[chaot]

Wrong concept - issue not clearly worked out.

The removal of this post does not disturb the context of this thread.
Summarized new post will be rewritten later.

[chaot]

ditto

[Terisa de morgan]

Originally Posted by eschwartz

Translation bug then -- third-party extensions and software without a multimillion-person userbase needs a little help getting foreign languages right

I don't think so. If I understand right, he's telling that the input field is too long and DoctorOhh doesn't see it. I see it too.... because the translated text is longer so the input field goes till the end. If we talk about bug, it would be not controlling the text length.

All this, of course, if I've understood it right (quite possible I haven't )

[eschwartz]

The bug is because of translations, thus it is a translation bug. Whether the bug is because of the translation, or the bug IS the translation, is immaterial.

FWIW -- sounded like both is true.

[chaot]

We shall come totally confused. That's what I've found with longer threads already repeatedly.

Originally Posted by Terisa de morgan

If I understand right, he's telling that the input field is too long and DoctorOhh doesn't see it. I see it too.... because the translated text is longer so the input field goes till the end.

Yes, I say the input field is to long. The same time I see that just as a matter of design. But a minority provision of sub-areas allows further conclusions about the quality in general. May be erroneously!

What @DoctorOhh has seen I do not know. At least he has reflected on something else: a putative translation bug (is immaterial as @eschwartz stated). And he missed that little Firefox icon on his Edit custom tag window.

Never lose sight of the 'red thread'.