ticket,summary,type,release,owner,status,created,modified,_description,_reporter
13937,change between wysiwyg to default editor makes WikiHtml content wrong.,enhancement,1.4,Jun Omae,new,2021-01-13T10:29:59+01:00,2021-03-22T10:46:18+01:00,"version: Trac 1.4.2
Changing the wysiwig editor to the default editor makes the contents strange.
The tested text is shown below.
{{{
default editor
{{{#!html
HTML Test
}}}
}}}
If I change from the default editor to the wysiwig editor, the content changes as shown below.
{{{
default->wysiwyg->default
{{{#!html HTML Test
}}}
}}}
When I change the editor again, HTML changes to monospace.
{{{
default->wysiwyg->default->wysiwyg->default->wysiwyg
`#!html HTML Test
`
}}}
Is this intended? Or does the wysiwyg editor not support WikiHTML format?
I'll be waiting for your reply. Thank you :)",mgs1994@…
13236,Monospace formatting and spaces,defect,1.0,Jun Omae,new,2017-07-13T12:28:36+02:00,2017-07-13T12:36:31+02:00,"Consider the text ""hello world"" in a single line: When selecting ""world"" and formatting it w/ monospace the plugin fails to properly format the text.
This applies to other ""portions of a line selected"" situations as well.
",fls@…
12260,Apache Bloodhound compatibility,enhancement,1.0,Jun Omae,new,2015-04-06T03:36:59+02:00,2015-04-06T03:36:59+02:00,"When I installed the latest version of TracWysiwyg plugin, It affected to the bloodhound wiki style (inner frame of the wiki has disappeared). So I changed the file wysiwyg.js line 79, insertBefore to appendChild. Now the bloodhound wiki style is not changed and I cannot find any bug yet.",unclok123@…
7391,Code block followed by tab removes all following text in wysiwyg mode,defect,0.12,Jun Omae,new,2010-07-20T06:40:49+02:00,2010-07-20T07:48:24+02:00,"Plugin Release: 0.12.0.2-r8148
Trac Release: 0.12
When a tab is placed after a code block, and changed to wysiwyg mode will remove all text after (and including) the code block. This can also remove large slabs of text in current pages when edited by users in wysiwyg mode.
Example:
{{{
This will show
}}}
{{{
This will be removed
}}}
And all text following will be removed when wysiwyg mode is used",AusAp
2453,Feature Request: Images in two clicks.,enhancement,0.12,Jun Omae,new,2008-01-22T12:17:19+01:00,2012-01-18T20:15:20+01:00,"Would be very nice: Image button in toolbar
1. Clicking this one pop up standard browse dialog
n. The file is added as attachment (transparently)
n. The Image macro is inserted at current position referencing that attachment
",anonymous
4641,TracWysiwygPlugin is working abnormally with DiscussionPlugin,defect,0.12,Jun Omae,new,2009-02-17T12:00:26+01:00,2009-02-17T12:00:26+01:00,"''I'm not sure that this ticket is for which plugin.
If this defect is not caused of TracWysiwygPlugin,
please reassign this ticket to DiscussionPlugin.''
When I edit a topic in a forum with wysiwyg editor (not textarea editor),
* abnormal scrolling with
* decoration-stripping with
|| '''Version Info''' ||
|| TracWysiwygPlugin: || 0.6 ||
|| DiscussionPlugin: || 0.2 ||
|| '''System Info''' ||
||Trac:|| 0.12dev-r7811 (upgraded from TOW)||
||Python:|| 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)] ||
||setuptools:|| 0.6c9 ||
||SQLite: ||3.3.4 ||
||pysqlite: ||2.3.2 ||
||Genshi: ||0.6dev-r999 ||
||Babel: ||1.0dev-r467 ||
||mod_python: ||3.3.1 ||
||Pygments: ||1.0 ||
||Subversion: ||1.5.1 (r32289) ||
||jQuery: ||1.2.6 ||
",nuclein@…
8308,Editor broken on Admin forms,defect,0.12,Jun Omae,reopened,2010-12-14T16:53:35+01:00,2011-02-08T10:25:19+01:00,"The editor is not usable on the Admin forms, due to the following issue:
* In both IE 8 and FF 3.6.12, the editor text box is not wide enough to see or use content.
Specifically, it fails on these Admin forms:
* Component
* Milestone
* Versions
Editor is working fine on the Ticket and Wiki forms.
We are running plugin 0.12 on Trac 0.12.1. On previous 0.11.x version the editor worked fine on all forms.
I will attach screenshots of IE and FF.",David Frahm
8387,Support for WikiCreole syntax,enhancement,0.12,Jun Omae,new,2011-01-10T18:44:55+01:00,2011-01-10T21:44:48+01:00,"It would be great if this plugin switched to (or had an option for) !WikiCreole syntax.
Thanks!",Mike Charles
8693,Wrong organized processors code due changing from wysiwyg to textarea edit view,defect,0.12,Jun Omae,new,2011-04-09T20:16:02+02:00,2013-12-03T12:40:02+01:00,"I wrote the following precessor code to view some table head elements:
{{{
{{{#!td
blub
}}}
{{{#!td
blub
}}}
}}}
After changing the view to ''wysiwyg'' and back to ''textarea'' (using the javascript bullet points) I got the following (the whole content lined up):
{{{
{{{#!td blub }}} {{{#!td blub }}}
}}}
Doing the view change another time brings up the following:
{{{
`#!td blub ` `#!td blub `
}}}
Unfortunately the output is weired as well.
Got this error with revisions 10050 and 9387 on both firefox and opera.",joerg04
8739,Auto preview in ticket comments does not work in wysiwyg mode,defect,0.12,Jun Omae,new,2011-04-27T10:57:18+02:00,2011-04-27T10:57:18+02:00,When I use textarea mode then on changing text of comment I see auto preview. In wysiwyg mode it does not work. This allows to fix any problems with display of comments before final submitting.,Ark
8857,Disable image pasting,defect,0.12,Jun Omae,new,2011-05-31T17:22:59+02:00,2011-05-31T17:22:59+02:00,"Would it be possible to disable the apparent ability to paste in images, since it doesn't actually save them?
This is very confusing to users, as they expect their images to be retained when pasted into a new ticket and saved. Ideally the images would be kept somehow, but seeing how this plugins works (converting everything into wiki syntax) that doesn't seem very feasible. I think it would be best not to trick the user into thinking they are actually saving an image.",anonymous
9886,Right/left/center justify table cells,defect,0.12,Jun Omae,new,2012-03-08T11:46:23+01:00,2012-03-08T11:46:23+01:00,"It should be possible to right/left/center justify the contents of table cells.
I attach a ""quick hack"" solution proposal, that uses the indent/outdent buttons to right/left justify the contents of table cells when the cursor is inside a table cell. It has been tested with fairly recent versions of Chrome and Firefox, and IE 8.",anonymous
11019,[patch] support intertrac link prefixes containing underscores (0.12),defect,0.12,Jun Omae,new,2013-04-16T10:54:24+02:00,2013-04-16T11:05:53+02:00,"The 0.12 version of the plugin (as of r12974) garbles trac links with intertrac prefixes that contain underscores, due to the regular expression used in the javascript code. Attached [attachment:tracwysiwygplugin_link_prefix_underscore_patch.diff patch] fixes this by adding underscore as an allowed character for the link prefix.
",jholg
7343,svn:https: links are handled inconsistently,defect,0.12,Jun Omae,new,2010-07-07T14:10:09+02:00,2010-07-07T14:10:09+02:00,"
I have inserted a ""svn:https:"" link in the wysiwig editor in the form
[svn:https:///svn/BEP/trunk trunk]
In the wysisiwg editor the link is shown as a link. In the page preview, the link is shown as plain-text, i.e. WikiFormatting does not work. I would appreciate if both would work the same and the editor would ignore these links.",markus.heinrichs@…
2742,How to make TracWysiwygPlugin the default handler,task,0.11,Jun Omae,new,2008-03-14T20:22:27+01:00,2017-06-02T08:34:02+02:00,"How can we set this module as the default handler for editing wiki?
It's nice that it saves user information choice (i.e. if I choose text block it will remember, and if i choose WYSIWYG it will remember)
But setting it as default would be good.
I ''thought'' you could do this in the trac.ini with:
{{{
[trac]
default_handler = TracWysiwygPlugin
}}}
but it doesn't work ... perhaps I have the module name wrong?",Matt Callaghan
2132,Issues with monospace formatting,defect,0.11,Jun Omae,new,2007-10-30T21:12:25+01:00,2007-10-30T21:12:25+01:00,"In all browsers I've tried this in, which includes Firefox 2.0.0.7, Firfox 1.5.0.12, and IE6, removing the monospace style from a selection of text causes that text to become deselected instead of remaining selected as is the case with the other styles.
Also, in IE6 the situation is worse. If a selection of text that includes the first word of a line has the monospace style applied, the style cannot be removed. And (again, in IE6) applying the monospace style to a selection that includes the first word of a long line that has been wrapped causes the line to become unwrapped and displayed on a single line.",Erik M. Bray
3340,Wysiwyg: Dislikes some nested definitions,defect,0.11,Jun Omae,new,2008-07-08T05:22:31+02:00,2015-07-20T20:31:37+02:00,"{{{
* C
l(s)::
* C
}}}
results in `Failed to activate the wysiwyg editor.`
",anonymous
3841,"Browser doesn't re-fill form on return, if plugin is enabled",defect,0.11,Jun Omae,new,2008-10-01T19:50:29+02:00,2013-08-07T05:02:49+02:00,"When editing a wiki page in Trac without this plugin enabled, if I accidentally press the browser's back button or follow a link to a different page (the roadmap for example) without first saving my changes, I can navigate back to the wiki page and my changes will still be there. When this plugin is installed, I can navigate back to the wiki page, but any changes I made disappear, which can result in lost work. Tested using Firefox 3.0.3.",Steve Strobel
4921,wysiwyg -> textarea transition loses [[BR]] tokens,defect,0.11,Jun Omae,new,2009-04-14T16:02:10+02:00,2009-04-14T16:02:10+02:00,"I have a wiki page that can be described as follows:-
{{{
= Welcome to the Wiki =
[[BR]]
[./ContactList Contact List]
[./Support Support Topics]
[./Development Development Topics]
[./Private Private area]
[[BR]]
}}}
When editing the page, if the ''wysiwyg'' selector is switched to ''textarea'', the {{{[[BR]]}}} tags become lost. Editting the page in either wysiwyg or textarea without making this switch is okay though.
Notable Versions:-
Server
* Trac 0.11.4
* TracWysiwygPlugin r5513
* Python 2.5
* MySQL 5.1.32
* Solaris 8
Client
* FF 3.0.8 & MS 6.0 (both)
* Windows XP SP2
Thanks for a nice tool otherwise.",colinwatt@…
6164,Enhancement Request: Right to Left Support,enhancement,0.11,Jun Omae,new,2009-11-05T23:23:30+01:00,2010-09-30T11:17:53+02:00,We use track in a multi-lingual environment. The lack of RTL support makes reading text written in some languages extremely cumbersome. It would be very useful to be able to switch between the two modes in this editor. I understand that this would ideally depend on the trac API offering adequate RTL support but it also seems like something that could be added via this otherwise invaluable plugin.,mohammad.dabiri@…
6479,Enhancement: Add ability to render trac linked images in WYSIWG editor panel,enhancement,0.11,Jun Omae,new,2010-01-22T12:05:30+01:00,2010-01-22T12:05:30+01:00,"At the moment if you include trac style image in a page referenced to an attached file, e.g.:
{{{
[[Image(something.jpg)]]
}}}
then the wysiwyg editor does not render the image but simply displays the raw trac tag.
Can this be enhanced so that the wysywig editor shows the rendered image in place.",anonymous
7006,"Add feature ""Insert Image"" (when is not an attachment)",enhancement,0.11,Jun Omae,new,2010-04-20T14:31:34+02:00,2022-06-07T07:29:35+02:00,"Is it possible to add a drop-down button to the bar for images with the following options:
* `[[Image(wiki:WikiFormatting:picture.gif)]]` (referring to attachment on another page)
* `[[Image(ticket:1:picture.gif)]]` (file attached to a ticket)
* `[[Image(htdocs:picture.gif)]]` (referring to a file inside project htdocs)
* `[[Image(source:/trunk/trac/htdocs/trac_logo_mini.png)]]` (a file in repository)
That's it. The plug-in is working perfectly besides that need.
Thanks!",fechex@…
7163,Not work the Back button in Opera 10.10,defect,0.11,Jun Omae,new,2010-05-25T14:55:59+02:00,2010-05-26T14:18:14+02:00,"At the Opera 10.10 the plugin TracWysiwygPlugin during the open to a ticket page does not work the Back button in browser. You have to click it several times (usually three times) instead of one.
We assume that the problem in code
{{{
d.open ();
d.write (html.join (""""));
d.close ();
}}}
in function TracWysiwyg.prototype.initializeEditor
When we commented out this code, then all was working correctly, except that in Wysiwyg mode, missing fonts.",Stas Agarkov
7212,Drop down menu to select and embed attachments in wiki pages,enhancement,0.11,Jun Omae,new,2010-06-07T15:06:38+02:00,2010-06-10T08:35:10+02:00,"
Add a drop down menu so that users will be able to select attachments uploaded to wiki pages. Once such selection is performed, image files should be embedded just like if image dialog box would be shown to the user. If not an image then only download link will be inserted (but specific control for preview would be nice as well ''' ;o) ''' .
",Olemis Lang
7694,Support for ColorMacro,enhancement,0.11,Jun Omae,new,2010-09-16T18:04:23+02:00,2010-09-16T18:04:23+02:00,It would be nice if this plugin would support integration with [wiki:ColorMacro].,Gasler Radu
8499,Ctrl + Tab indents the bullet points.,enhancement,0.11,Jun Omae,new,2011-02-14T05:04:46+01:00,2013-12-03T12:36:59+01:00,"Ctrl + Tab indents the bullet points when using the wysiwyg mode but also changes to the next tab.
I think the correct behaviour should be moving to the next tab in the browser but not indenting the bullets.
I am using Firefox 3.6.13 in Ubuntu 10.04. Straight from the repository.",andhos@…
8860,Plugin changes status-radio-buttons on reload of page,defect,0.11,Jun Omae,new,2011-06-01T15:38:42+02:00,2011-06-01T16:46:57+02:00,"Example:
Ticket is in status new, radio button ""leave as new"" is selected. If a page reload occures (with F5 or pressing return in address bar), the action changed so the button ""leave as new"" is no longer selected.",jjk
2108,Enhancement Request: Can you add highlighting support to the toolbar,enhancement,0.10,Jun Omae,new,2007-10-25T22:12:47+02:00,2007-11-15T15:53:36+01:00,"Nice work on the plugin. Was wondering if you can add highlighing support to the toolbar.
Thanks",ashishg@…
2118,list + code block formating breaks ...,defect,0.10,Jun Omae,reopened,2007-10-29T07:02:56+01:00,2008-08-26T15:24:47+02:00,"a formatting like the following gets broken by wysiwyg editor:
1. first
{{{
first block
}}}
1. second
{{{
second block
}}}
and there the text continues
the source is
{{{
1. first
{{
first block
}}
1. second
{{{
second block
}}
}}}",rupert thurner
2138,"IE6, HR doesn't work right",defect,0.10,Jun Omae,new,2007-11-01T15:15:21+01:00,2007-11-01T15:15:44+01:00,If you have an HR with content after there is a fake/phantom paragraph between the HR and the following content. If you click there the cursor appears but if you type the text appears above the HR. It's annoying but doesn't keep the user from doing their job in most cases.,Jason Winnebeck
3630,Can Autolink be configured as OFF by default?,enhancement,0.10,Jun Omae,new,2008-08-29T14:47:28+02:00,2017-09-07T17:03:16+02:00,"I have issue with plugin default behavior. The project I am documenting uses CamelCase extensively and default autolink makes it tiresome to unlink all the occurrences.
Is it possible to add to plugin configuration default value for Autolink, or to remember the last state of it?
Thanks.",cxdood@…
2188,Quotation handling on lastrow is broken,defect,0.10,Jun Omae,new,2007-11-16T12:15:15+01:00,2013-12-03T15:07:44+01:00,"When pressing ""reply"" it's hard to write actual reply, since usually can't go beyond quoted text and quotation marks stays on.
Workaround is to go back to text mode, write foobar text and then switch back to wysiwyg mode.
When replying editing should start on a new line / paragraph after quotation.
",jtiai
2219,add a line to a codeblock is inconsistent,defect,0.10,Jun Omae,new,2007-11-25T18:09:55+01:00,2008-05-25T19:43:38+02:00,"pressing return in a code block is not doing the same in all code blocks.
=== normal ===
pressing return adds a line in the code block. if the code block is at the end of a page would be nice that pressing return twice would end the code block and switch to text mode.
=== in a list ===
in a list like mentioned in #2118, pressing return makes another list entry. it would be nice if pressing return in the middle of a code block would just add a new line.
",rupert thurner
2273,HTML Image file automatic link,enhancement,0.10,Jun Omae,new,2007-12-06T04:53:23+01:00,2007-12-06T04:55:08+01:00,"If you copy a web page that contains images, and then paste it into tracWysiwyg, the picture will appear in the wysiwyg window.
However, there is no wiki syntax to handle the picture.
Ideally, it would be nice if it can convert the ![]()
tag objects into [[Image(src)]]",anonymous
2300,autolink switches off instead linking in ie6,defect,0.10,Jun Omae,new,2007-12-12T19:34:14+01:00,2007-12-12T19:34:14+01:00,"when autolink is activated and you try to insert a link like WikiFormatting it switches off automagically and the link is not set. ie6, windows xp.
",rupert thurner
2699,doesn't work on startpage,defect,0.10,Jun Omae,new,2008-03-07T12:22:22+01:00,2008-03-07T12:22:22+01:00,"the WYSIWYG plugin doesnt work on the main wiki page (the startpage) a javascript alert box says: ""Failed to start the wysiwyg editor""
the javascript debugger says:
{{{
target has no properties
[Break on this error] holder = target.parentNode;
}}}
",rcoenen
2934,keeping cursor position between wysiwyg mode and normal mode,enhancement,0.10,Jun Omae,new,2008-04-20T03:04:58+02:00,2008-04-20T03:04:58+02:00,"When I edit a long wiki-page, If I change mode between wysiwyg-mode and normal-mode then cursor position of text area move to top.
I want to keep previous mode's cursor position.
It's very convinient to check result quickly.
I don't know the platform support function to impliment such operation.",redboltz
2944,Change behavior of URL drag-and-drop,enhancement,0.10,Jun Omae,new,2008-04-24T01:17:10+02:00,2008-06-20T23:41:51+02:00,"a highly desirable enhancement to the already amazing TracWysiwygPlugin would be to modify the behavior when you drag-and-drop a url from one browser window into a TracWysiwig editor.
steps to repro
1. in one browser window, open a trac page with a wysiwig editor (eg. wiki edit, ticket, etc)
1. in another browser window, load your favorite web page, let's say [http://trac-hacks.org/wiki/TracWysiwygPlugin TracWysiwygPlugin]
1. drag the url from the browser's address bar into the wysiwig editor
desired result
* a link to the url http://trac-hacks.org/wiki/TracWysiwygPlugin gets created with the text from the of that page (in this example, ""TracWysiwygPlugin - Trac Hacks - Plugins Macros etc. - Trac""). i.e. in wiki markup, something like:
{{{
[http://trac-hacks.org/wiki/TracWysiwygPlugin TracWysiwygPlugin - Trac Hacks - Plugins Macros etc. - Trac]
}}}
actual result (using firefox 2.0.0.14, trac 0.10.4, TracWysiwyg 0.2-r3414)
* just the raw url with no surrounding [] that gets linkified by trac (wiki markup):
{{{
http://trac-hacks.org/wiki/TracWysiwygPlugin
}}}
i don't know anything about python, trac plugins or drag-and-drop, but i think this should be possible since repeating the steps above and dragging a url into a normal textarea results in the following wiki markup:
{{{
http://trac-hacks.org/wiki/TracWysiwygPlugin
TracWysiwygPlugin - Trac Hacks - Plugins Macros etc. - Trac
}}}",anonymous
13742,WikiFormatting hint is poorly positioned on ticket page,defect,,Jun Omae,accepted,2020-01-31T01:54:39+01:00,2021-01-27T05:34:30+01:00,"New ticket page:
[[Image(Screen Shot 2020-01-30 at 16.50.38.jpg,100%)]]
Ticket page:
[[Image(Screen Shot 2020-01-30 at 16.50.56.jpg,100%)]]
[[Image(Screen Shot 2020-01-30 at 16.51.15.jpg,100%)]]
Maybe we should just hide the hint on the ticket page?",Ryan J Ollos