Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#3900 closed Bug (invalid)

Extract tags are getting displaced in the source of the content

Reported by: Steve Organ Owned by:
Priority: Normal Milestone:
Component: Core : Styles Version: FCKeditor 2.5 Beta
Keywords: Cc:


STEP -1: - I am trying to make Background section of the content as Extract=1, "Identifying Berklee customers" section of the content as Extract=2, "Call-handling exceptions" section of the content as Extract=3

STEP - 2: - I clicked on Source and added 3 <Extract> tags. <Extract id="1">, <Extract id="2">, <Extract id="3"> in the source as shown below around these 3 sections of the content

STEP -3: - I just switched between the content and the source view again to verify if the tags I added are still looking good, and I saw the tags were displaced by the system and here is the screen shot for the same. There is no content present inside the tags now.

I have tried it couple of times in different articles but seeing the same behavior in all of them, Some times, the <Extract> tag I added around the content was removed all together instead of the displacement in some scenarios.

Attached are screenshots : Picture 5 Shows the content that we are working with to start.

Picture 7, 8, &amp; 9 are where and how we inserted the tags 7 = tag 1, 8 = tag 2, and 9 = tag 3\.

Then Pictures 18, 19, 20 show how the close tag moves with no intervention in the same order respectively 18 = tag 1\.\.\.and so on\.

Attachments (1)

ScreenShots & (732.3 KB) - added by Steve Organ 15 years ago.

Download all attachments as: .zip

Change History (6)

Changed 15 years ago by Steve Organ

Attachment: ScreenShots & added

comment:1 Changed 15 years ago by Steve Organ

we have a homegrown JAVA connector for server side implementation. So if this is related to server side configuration that this could be an issue on our end.

comment:2 Changed 15 years ago by Steve Organ

Any status on this issue? Let me know if further clarification or information is necessary.

Thanks, Steve

comment:3 Changed 15 years ago by Alfonso Martínez de Lizarrondo

Resolution: invalid
Status: newclosed

You are using a non existing "Extract" tag, so the browser has an undefined behavior in that situation.

That's it: the behavior that you get is not the one that you want, but it's up to you to find out how to fix it as you are the ones that have created that new tag.

comment:4 Changed 15 years ago by Steve Organ

just to be more clear on your response, are you saying that the fix would have to reside on the end-user's browser?

What typically would you have to do to define tags so that the browser can recognize these tags?

comment:5 Changed 15 years ago by Alfonso Martínez de Lizarrondo

I'm not sure what "end-user" means to you. I'm talking about the person that will use the editor. They use a browser, and you have to study what happens in that browser(s) when they find some custom tags.

Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy