{5} Assigned, Active Tickets by Owner (Full Description) (16 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
jf.hovinne
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #20 | Link Edit broken in Firefox (2.0.0.3) | Editor | 0.6 | defect | 04/24/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I am unable to edit existing links in Firefox. When I put the cursor on a link and click the Link-button the window pops up as normal with the correct values in the textboxes. But when I click Submit, the window closes but no changes are made on the link. I tested the same thing on the same page in IE7, and that worked fine. Regards David |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #69 | Firefox: links issues | Editor | 0.5 | defect | 07/22/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Under Firefox I've found few issues whit links adding/editing/pasting.
1. Adding a link: while adding a link containing the ampersand character (&) - ampersand is "escaped" to "&" in very strange way. 2. Editing: this issue was described at ticket 20. Solution given by jf.hovinne (select entire link to edit) wont work - if we select entire link we get in edit pop-up no data. In fact - we cannot edit links in Firefox, we have to create them from scratch.
3. Pasting relative links: when pasting to editor relative link, for example: All issues observed using Firefox 2.0.0.5 on Windows and WYMeditor from SVN (rev 396) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #79 | line breaks don't work properly | Editor | 0.5 | defect | 09/30/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When I try to enter a line break <br /> by pressing shift-enter, the cursor moves a little to the right. There is no new line created. When I enter a space after that, the new line is created, containing the space. Pressing backspace remove the space and the new line. Next, when I press shift-enter again, the new line comes back immediately. However the padding between the current paragraph and the next paragraph disappears. (tested in IE 6.0.2800) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #126 | Buttons do not work on Firefox 3 /w Silver skin | Editor | 0.5 | defect | 09/29/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I can reproduce the issue with Firefox 3.0.3 on the example: http://files.wymeditor.org/wymeditor/trunk/src/examples/13-silver-skin.html None of the buttons work. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #134 | removeEmptyTags - removes content | Editor | defect | 10/15/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
We have some really not great RTF files, which we are importing using copy/paste to wymeditor. There is non-breakable space after preposition, and because the RTF files are not very good (export from QuarkPress) it sometimes produces (it's visible for example in OpenOffice toolbar that the space is really in italics) z<em> </em>test and the whole non-breakable space is removed by removeEmptyTags resulting into: ztest (so the space is removed) resulting into broken text. If I understand it correctly the removeEmptyTags method should remove tags which are "around" white space and thus are not necessary. So imho it should be: return xhtml.replace(new RegExp('<('+this.block_tags.join("|")+')>(<br \/>| | |\\s)*<\/\\1>' ,'g'),'$2'); istead of: return xhtml.replace(new RegExp('<('+this.block_tags.join("|")+')>(<br \/>| | |\\s)*<\/\\1>' ,'g'),); |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #63 | BlockUI instead of popup windows. | Editor | 0.6 | enhancement | 07/15/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
It would be great to have overlay dialogs using BlockUI (http://malsup.com/jquery/block/) instead of popup windows. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #130 | Automatically Resizeable iFrame | Editor | 0.5 | enhancement | 10/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Can we make an option to automatically resize the iframe height? I tried to do some iframe hacks I found on the web but it seems we should hook the resize to an action that wymeditor is doing (keypress?). Thank you. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #138 | onchange or isdirty functionality | Editor | 0.6 | enhancement | 10/30/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I'm looking to implement an auto-save style bit of functionality to my editor. The problem I'm having is that I can't figure a simple way to tell if the content of the editor have changed through any other method than checking the calling update() and checking the new contents versus the old (which is way more computationally expensive than it needs to be, especially on long documents). A simple variable/function that keeps track of whether or not there have been any changes to the editor since the last update() would be very helpful. TinyMCE calls this isDirty and I believe it will help solve the issues that these people are running in to also. It's not as elegant as a real onchange event, but it's effective for use in polling for changes. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #98 | iframe flickers and jumps in IE6 when instance created inside a table | Editor | defect | 03/05/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
In IE6 ... When WYMeditor is instantiated inside a simple table, the iframe scroll bars blink/dance when the mouse is moved from the surrounding box over the iframe edge. Furthermore if enough content is entered and the iframe has to scroll, and the user scrolls to the bottom of the content, then selects content in order to bold or italicise it, when they move the mouse out of the iframe towards the toolbar button, the iframe scrolls back to the top meaning the user loses all context and must scroll down again. I have a test case here: http://devel.webutils.vicnet.net.au/wymtest/index.cgi The test case is almost identical to the 01-basic.html file that was released with version 0.4 as an example. I've also created a video of the symtoms here: http://devel.webutils.vicnet.net.au/wymtest/IE6-table-blinkDanceScroll.avi The test case is using version jQuery packed version 1.2.1 Thanks pd |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #99 | table attribute cellspacing being stripped out | Editor | 0.5 | defect | 03/07/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Ok, this is an odd one. I am trying to insert some HTML using the HTML view of the WYMedotor. I paste in some code where one of the lines is: <table cellspacing="0" cellpadding="5" class="basic"> BUT after the form is submitted, the code comes out with the same line looking like: <table class="basic" cellpadding="5"> Now can you please explain to me why are these tags in different order, and more importantly, where is the cellspacing attribute? Thanks, -Roman |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #121 | Classes won't apply to images in certain situations | Editor | 0.5 | defect | 09/19/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I am attempting to place images into a textarea and then apply a custom class to float left or float right. While doing this, I noticed that the classes would stop applying when certain things were done. Here are the steps that I followed to create the problem, using both methods that caused it Method 1:
1. Open WYMEditor and type a paragraph of text. Method 2:
1. Open WYMEditor and type a paragraph of text. In method 2, I also noticed that the URL would change drastically. "/images/image.jpg" would become "../../../images/image.jpg". The only method that reliably implemented the class was this:
1. Open WYMEditor and type a paragraph of text. It only appeared to break if I moved the image before putting the class or if I added the image manually through HTML. I've attached the custom CSS file I am using for this. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #12 | Request for Special Characters feature | Editor | 0.5 | enhancement | 03/18/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I have run into a real-world situation where one of the users of SkyBlueCanvas with Wymeditor needs to be able to insert html special characters without editing the raw HTML (¨ » etc.). I think this is going to be a necessity in a fully developed version of Wymeditor. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #17 | Anchor relationship | Editor | 0.5 | enhancement | 04/08/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
To futher improve the semantic and accessibility aspects of the anchor element I think support for the rel attribute is nessecary. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #59 | Make Indent/Outdent buttons gray out when not applicable | Editor | 0.5 | enhancement | 06/30/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I have users that want to use the "indent" button to indent paragraphs (when it is obviously done with the css on the page. Any chance we could gray out these buttons when they don't apply? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #135 | Unable to add containers to list items | Editor | 0.6 | enhancement | 10/16/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
It does not seem possible to add a container inside a list item (li) even though it is valid xhtml. For example: <ul>
<li>
<h3>My title</h3>
<p>A description</p>
</li>
<li>
<h3>Another title</h3>
<p>A description</p>
</li>
</ul>
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #136 | Use a custom alias for jQuery | Editor | 0.6 | enhancement | 10/17/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
While the plugin correctly avoids overwriting/assuming the $ variable, it would be wonderful if the plugin used a custom alias (via closure), which would help it run in a high-conflict environment. http://docs.jquery.com/Plugins/Authoring#Custom_Alias_in_plugin_code As described, wrapping the plugin in (function($) {
// plugin definition
})(jQuery);
seems to be the best practice in jQuery plugin development (note that the official jQuery UI plugins do this). This allows the function to run in environments where the jQuery variable can't always be assumed (i.e. after WYMeditor's initialization, the variable "jQuery" may be deleted, overwritten, or renamed.) This is a small and simple change that would save me from having to manually do it to each WYM release, and being able to change all current instances of "jQuery" to "$" would be a tiny size optimization, too. :) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||