#234: Microsoft Asp.net 2.0 AJAX UpdatePanel Bug
-------------------------------+--------------------------------------------
Reporter: Anksunamon | Owner: fredck
Type: Bug | Status: assigned
Priority: Normal | Milestone: FCKeditor 2.6.3
Component: Server : ASP.Net | Version: FCKeditor 2.4
Resolution: | Keywords: Confirmed HasPatch
-------------------------------+--------------------------------------------
Comment(by fredck):
Replying to [comment:42 serializer]:
> FredCK's patch is better in that it doesn't require an extra .js include
- which my AJAX solution does. However in terms of architecture, it's
bringing ASP.NET-specific code into the fckeditor core, breaking the usual
separation of the server-specific implementions as separate components
from the core editor.
I was aware of that and actually checked the effective impact of it in the
core code... ~370 Bytes. So, that would not be a big issue, considering
the importance of this compatibility fix.
> Another concern is that the _onSubmitStatements object is an internal
feature of PageRequestManager which *could* be subject to change in future
releases, since it's not publicly specified or documented. (Unlikely I
admit, but a potential gotcha...)
I was pretty unhappy with it too. I've actually minimized the usage of
"private" stuff to avoid possible incompatibilities. I've also checked if
anything got changed in this sense since the .Net 2.0 and the 3.5 and
everything we use here looks the same. But, this thing still makes me
worried too. Only MS knows what could happen with .Net 4.0 or whatever. It
could work for a temporary solution though. We always have the chance to
fix it in the future.
> Another problem would be if a different Javascript framework decided to
name something Sys.WebForms.PageRequestManager... again very unlikely but
would cause unexpected problems!
Unlikely to happen, but I've added it into a "try" block just in case.
> A further problem I'm not sure about, is what would happen if the
fckeditorapi code ran *before* the PageRequestManager had loaded?
Personally I don't know enough about the Javascript pipeline in different
browsers to know how possible this is. Basically, are scripts *guaranteed*
to be executed in the order that they are referenced in the page, or are
they just executed as soon as they're downloaded?
This is not an issue because the API will get called only when the editor
is loaded, far later the page loading completion.
----
So, [attachment:234.patch] is still a possible solution. I've avoided
other things to not introduce unwanted dependencies to the FCKeditor.Net
assembly.
But, I still wanted to give it a try by using reflection. So, here we have
the [attachment:234_2_FCKeditor.patch] and
[attachment:234_2_FCKeditor_Net.patch] patch files for it. It also
introduces the PreventSubmitHandler setting.
What do you guys think about this one now? What should be the way to go?
--
Ticket URL: <http://dev.fckeditor.net/ticket/234#comment:43>
FCKeditor <http://www.fckeditor.net/>
The text editor for Internet
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
FCKeditor-Trac mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fckeditor-trac
