I was writing some aspx pages when i experimented a strange issue.
I have a div tag like this:
<div id="divCourses1" style="<%=GetDisplayStyle(eidlevel,
arrIdLevel[0])%>">
Now, as long as i don't switch the page to HTML into Design everything
works fine.
But if i switch the page into Design and therefore into HTML again,
then all the attribute style and its content disappear.
I have tryed many times and the behavior is always the same.
Anyone knows anything about that issue? It's a known issue?
I would avoid to use html runat-sever objects, if possible.
Thanks.2003 does bad things when switching between HTML and Design view, it is a
known issue and the only way to fix it is to migrate your code to 2005 :(
The solution I would recomment is to your a runat=server object, but i see
you have reservations against that.
Karl
--
http://www.openmymind.net/
"Joneleth" <Joneleth_76@.hotmail.com> wrote in message
news:1139391607.599439.317260@.z14g2000cwz.googlegr oups.com...
> Hi
> I was writing some aspx pages when i experimented a strange issue.
> I have a div tag like this:
> <div id="divCourses1" style="<%=GetDisplayStyle(eidlevel,
> arrIdLevel[0])%>">
> Now, as long as i don't switch the page to HTML into Design everything
> works fine.
> But if i switch the page into Design and therefore into HTML again,
> then all the attribute style and its content disappear.
> I have tryed many times and the behavior is always the same.
> Anyone knows anything about that issue? It's a known issue?
> I would avoid to use html runat-sever objects, if possible.
> Thanks.
Karl Seguin [MVP] wrote:
> 2003 does bad things when switching between HTML and Design view, it is a
> known issue and the only way to fix it is to migrate your code to 2005 :(
ok.
> The solution I would recomment is to your a runat=server object, but i see
> you have reservations against that.
> Karl
After trying for several minutes i realized you're right. :)
I see no other way than using server-side objects to avoid that bug.
Thanks.
0 comments:
Post a Comment