If you think this add-on violates Mozilla's add-on policies or has security or privacy issues, please report these issues to Mozilla using this form.
Please don't use this form to report bugs or request add-on features; this report will be sent to Mozilla and not to the add-on developer.
No keyboard shortcuts for formatting? What is the point of this? All forums already have a toolbar for the encoding. I was expecting a richtext-like WYSIWYG text area that can then be converted to BBCODE.
Suggestion for grammar correction in the "About this Add-on" description.
EditING can be done in the form or in a new tab. Some extensionS for the BBComposer...
Here is a small CSS hack to append to userChrome.css in "Chrome" directory in your Firefox profile:
background-color: rgb(235, 235, 235) !important;
(or whatever light color that you would like to see painted on the background)
It is bold and stinky but it works :p
Much more useful than BBCode because I don't want to keep right-clicking to modify a post.
Looking forwards to more features and hopefully embedding with a button instead of the context menu. That will grab the final star.
4 out of 5
ahh ok reinstalled and it is working now
To fulfil my needs I suggest adding shortcuts to typical buttons, ie. Bold, italic etc.
We will try to make it for the 3.1 version (3.0 is already done). Thanks for using BBComposer, wich you have fun to use it.
I guess it works, but its not the best. If it had as complex WYSIWYG as some of the HTML editors on this site, that would be great. Simple options such as aligning text is not supported, and its kind of like a giant obtrusive glob on the bottom of firefox instead of being built into the textarea. Good work though! Hope it gets better soon, I'm using BBCode for now, although that unfortunately only works with the context menu.®
Good addon, but breaks double click functionality, needed to select some text for the purposes oter than editing (e.g., for copying and translating). This bothers me much.
When I double click some text in a textarea,
BBComposer unexpectedly appears, and I could not find a way to change this behaviour.
Error message also pops up:
"The content has been modified during the transfert because it contains unexpected content for the language you choose.
Orphelin inline nodes detected, creating new paragraph to contain them."
I use FF 3.0.10 Russian with BBComposer 2.0.
Thanks for reporting issues. In the next version (probably soon reviewed by amo editors), i disabled this double-click edition by default. It will only be editable by double-clicking when the textarea appears in the "saved textareas".
The alert is because when editing with BBComposer, XHTML is default language. In this language, text must be in paragraphs. So, the editor alert user that the text will be included in a new paragraph. Maybe there are another way to show it to the users, but i didn't found yet.
Thanks for your help !
Very good work! Thanks for this extension. But it'll be great if you add support for align tag in the BBCode editor.
The next bbcomposer's version will purpose this nex functionnality, thanks to use BBComposer.
Very good idea, but useless in wiki. After switching to Wiki code all already entered text colapses and it's hard to read it. Inserting 'enter' between colapsed lines makes BBComposer to put tags which are unrecognized by Wiki.
I just cannot edit my wiki pages with it. Sorry.
I'm happy to get some advice about the wikimedia support. I'll try to make better conversion but one thing you have to know is that it will never support every wikimedia code.
Some of those codes are interpreted by the server and correspond to things that are in the database. As i wrote in the official website, it's just a "basic" support of wiki.
Thank you for the time you spend to tell me what you're thinking about BBComposer.
I am testing BBComposer right now in a large red font.