id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
14511	#14509 closed Bug (invalid) Editor appears to remove hand-coded styles in span in Chrome	Don		"Closing the ticket without letting me respond is poor customer service!

Your response...

''The only reason why editor might remove spans is because of ACF but this feature is not browser dependent. If this is happening in single browser and after saving data on server-side then you need to check third-party plugins installed in chrome and your server-side code. It is most likely one of those areas which is causing your problem''

First, ONLY PART of the span style is removed, specifically ID, FLOAT, and WIDTH.

Second, I ALREADY verified the server-side code was not doing this by checking it BEFORE setting a ticket - I don't like wasting other's time.

Third, the fact that another browser stores the identified properties properly was a clue that Chrome and the Editor were interacting unexpectedly not the server.

And fourth, I reviewed the documents regarding ACF.  During that review, I found no references to:

1. Browser specific issues -- i.e. Chrome vs Firefox
2. Where is the list of PROPERTIES that are initialized as ""disallowed by default""?  I understand that when certain buttons are not displayed in the toolbar, those TAGS are disallowed, but the text does not list how the AUTOMATIC PROPERTY DISALLOWANCES occur -- except if I engage them, and I have not done that.

While ''this feature is not (supposed to be) browser dependent'' is a nice sentiment, the challenge I am facing IS.  I even went to the point of a different computer, and new install of Chrome and Firefox.  

There, I confirmed that on Chrome (but not Firefox) the properties ID, FLOAT, and WIDTH are removed from the content.

SO...
1.  I have eliminated server-sides as culprit ...
2.  I have eliminated ADDONS as culprit ...
3.  I have reviewed ACF for cause and found none.
4.  AND CONFIRMED Chrome-CKeditor specific interaction.

Now, how about we try this again, instead of blowing me off.

"	Bug	closed	Normal		General	4.5.7	duplicate