[jQuery] Re: Back Button
I found a way to work with Klaus's plugin. But, one problem has come
up.
My URLS work - and look like this:
a href=/Alfredo title=Alfredo class=remote
onclick=$.Content_SearchTag('Pasta','Alfredo');Alfredo/a
However, the destination behind this link also has similar links on
it. When it is delivered into the proper div area on the layout, the
links that come with it replace the page instead if staying scoped in
the div.
I did try calling $.ajaxHistory.initialize(); again after the div is
loaded. No impact. Anyone have any ideas/experience on that? The
examples on Klaus's site do not have sublinks.
Thanks much!
On Nov 26, 10:11 pm, Brian Cherne [EMAIL PROTECTED] wrote:
Both history plug-ins apply the onclick logic for you.
http://www.mikage.to/jquery/jquery_history.html
With Mikage's history plug-in you'll need a pageload function (see the
source code) and edit it according to the hash values of your anchor tags.
I'd recommend replacing his if(hash) statement with a switch(hash) statement
if you're going to be handling each hash differently. However, note in the
off-course part of this thread another user mentioned having trouble with
IE7 and Mikage's plug-in. YMMV.
http://stilbuero.de/jquery/history/
Klaus' more recent history plug-in looks much more like jQuery syntax. You
target an anchor tag using regular old jQuery selectors and the .history
method takes a function as its parameter. So an anchor tag like:
a id=linkToHome href=#homeHome/a
...could be accessed using:
$('#linkToHome').history( showHome() );
Klaus' history plug-in also has a built in remote method that pulls the
HTML file that is linked to in the anchor tag. You can use that if it works
better in your situation.
Good luck,
Brian.
On Wed, Nov 26, 2008 at 6:46 AM, OhNoMrBill [EMAIL PROTECTED] wrote:
I am bounding this follow-on question up...thread kind of went off
course.
The bit about links makes sense; but then how do I bind the javacsript
onclick functions to the links?
On Nov 24, 5:29 am, OhNoMrBill [EMAIL PROTECTED] wrote:
That makes sense; but then how do I bind the functions to the links?
The functions represent a large block of black-boxed code that is an
AJAX handler that pushes content into destination divs.
On Nov 24, 2:52 am, Brian Cherne [EMAIL PROTECTED] wrote:
Take a look at the history plug-in page code again:
http://www.mikage.to/jquery/jquery_history.html
A really important concept to understand is that the history plug-in
(any
history plug-in) is listening / watching for the URL to change. Any
change
you want it to make going Back you will need to let it make going
Forward (and on click) as well. You basically relinquish control to
the
history plug-in (actually to the pageload function if you're
following the
example URL to the letter). It works like this:
- user clicks link with an #home href
- url changes to page.html#home
- history plug-in notices url change, calls pageload function
- pageload function does something based on home
- user clicks link with an #products href
- url changes to page.html#products
- history plug-in notices url change, calls pageload function
- pageload function does something based on products
- user clicks browser's Back button
- url changes to page.html#home
- history plug-in notices url change, calls pageload function
- pageload function does something based on home
- user clicks browser's Forward button
- url changes to page.html#products
- history plug-in notices url change, calls pageload function
- pageload function does something based on products
I hope this makes sense. You will need to:
1) remove the inline onclick for each of your links. That overrides the
history plug-in and you won't be able to work around it (cleanly).
2) make the href hash values different for each of your links.
So, instead of:
a href=# onclick=showHome()Home/a
You'll need something more like:
a href=#homeHome/a
a href=#productsProducts/a
I hope this helps.
Brian.
On Sun, Nov 23, 2008 at 10:51 PM, OhNoMrBill [EMAIL PROTECTED]
wrote:
Anyone have an ideal on this?
On Nov 22, 8:15 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
I am in a real bind on this issue. Is anyone able to answer? Help
would be greatly appreciated if you can!!
On Nov 22, 10:50 am, OhNoMrBill [EMAIL PROTECTED] wrote:
Here is the scenario I am trying to deal with currently:
I have a link that looks like:
a href=# onClick=$.Content_Home();Some Link/a
All the url links in this site look like this...onclick
overrides.
What I need to do is ensure that when a user clicks back, the
actual
prior jQuery function is called, and not the entire page.
I tried the history plugin, and can not seem to get it to pick
this
kind of thing up
[jQuery] Re: Back Button
OK, I think most iof this makes sense. The one bit where there is a
gap for me is as follows:
We have both:
a id=linkToHome href=#homeHome/a
and
$('#linkToHome').history( showHome() );
Ho do I associate showHome() with the link linkToHome in the
first place?
On Nov 26, 10:11 pm, Brian Cherne [EMAIL PROTECTED] wrote:
Both history plug-ins apply the onclick logic for you.
http://www.mikage.to/jquery/jquery_history.html
With Mikage's history plug-in you'll need a pageload function (see the
source code) and edit it according to the hash values of your anchor tags.
I'd recommend replacing his if(hash) statement with a switch(hash) statement
if you're going to be handling each hash differently. However, note in the
off-course part of this thread another user mentioned having trouble with
IE7 and Mikage's plug-in. YMMV.
http://stilbuero.de/jquery/history/
Klaus' more recent history plug-in looks much more like jQuery syntax. You
target an anchor tag using regular old jQuery selectors and the .history
method takes a function as its parameter. So an anchor tag like:
a id=linkToHome href=#homeHome/a
...could be accessed using:
$('#linkToHome').history( showHome() );
Klaus' history plug-in also has a built in remote method that pulls the
HTML file that is linked to in the anchor tag. You can use that if it works
better in your situation.
Good luck,
Brian.
On Wed, Nov 26, 2008 at 6:46 AM, OhNoMrBill [EMAIL PROTECTED] wrote:
I am bounding this follow-on question up...thread kind of went off
course.
The bit about links makes sense; but then how do I bind the javacsript
onclick functions to the links?
On Nov 24, 5:29 am, OhNoMrBill [EMAIL PROTECTED] wrote:
That makes sense; but then how do I bind the functions to the links?
The functions represent a large block of black-boxed code that is an
AJAX handler that pushes content into destination divs.
On Nov 24, 2:52 am, Brian Cherne [EMAIL PROTECTED] wrote:
Take a look at the history plug-in page code again:
http://www.mikage.to/jquery/jquery_history.html
A really important concept to understand is that the history plug-in
(any
history plug-in) is listening / watching for the URL to change. Any
change
you want it to make going Back you will need to let it make going
Forward (and on click) as well. You basically relinquish control to
the
history plug-in (actually to the pageload function if you're
following the
example URL to the letter). It works like this:
- user clicks link with an #home href
- url changes to page.html#home
- history plug-in notices url change, calls pageload function
- pageload function does something based on home
- user clicks link with an #products href
- url changes to page.html#products
- history plug-in notices url change, calls pageload function
- pageload function does something based on products
- user clicks browser's Back button
- url changes to page.html#home
- history plug-in notices url change, calls pageload function
- pageload function does something based on home
- user clicks browser's Forward button
- url changes to page.html#products
- history plug-in notices url change, calls pageload function
- pageload function does something based on products
I hope this makes sense. You will need to:
1) remove the inline onclick for each of your links. That overrides the
history plug-in and you won't be able to work around it (cleanly).
2) make the href hash values different for each of your links.
So, instead of:
a href=# onclick=showHome()Home/a
You'll need something more like:
a href=#homeHome/a
a href=#productsProducts/a
I hope this helps.
Brian.
On Sun, Nov 23, 2008 at 10:51 PM, OhNoMrBill [EMAIL PROTECTED]
wrote:
Anyone have an ideal on this?
On Nov 22, 8:15 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
I am in a real bind on this issue. Is anyone able to answer? Help
would be greatly appreciated if you can!!
On Nov 22, 10:50 am, OhNoMrBill [EMAIL PROTECTED] wrote:
Here is the scenario I am trying to deal with currently:
I have a link that looks like:
a href=# onClick=$.Content_Home();Some Link/a
All the url links in this site look like this...onclick
overrides.
What I need to do is ensure that when a user clicks back, the
actual
prior jQuery function is called, and not the entire page.
I tried the history plugin, and can not seem to get it to pick
this
kind of thing up. Anyone with direct experience on this kind of
thing,
please chime in with some suggestions.- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
[jQuery] Re: Back Button
I am bounding this follow-on question up...thread kind of went off course. The bit about links makes sense; but then how do I bind the javacsript onclick functions to the links? On Nov 24, 5:29 am, OhNoMrBill [EMAIL PROTECTED] wrote: That makes sense; but then how do I bind the functions to the links? The functions represent a large block of black-boxed code that is an AJAX handler that pushes content into destination divs. On Nov 24, 2:52 am, Brian Cherne [EMAIL PROTECTED] wrote: Take a look at the history plug-in page code again: http://www.mikage.to/jquery/jquery_history.html A really important concept to understand is that the history plug-in (any history plug-in) is listening / watching for the URL to change. Any change you want it to make going Back you will need to let it make going Forward (and on click) as well. You basically relinquish control to the history plug-in (actually to the pageload function if you're following the example URL to the letter). It works like this: - user clicks link with an #home href - url changes to page.html#home - history plug-in notices url change, calls pageload function - pageload function does something based on home - user clicks link with an #products href - url changes to page.html#products - history plug-in notices url change, calls pageload function - pageload function does something based on products - user clicks browser's Back button - url changes to page.html#home - history plug-in notices url change, calls pageload function - pageload function does something based on home - user clicks browser's Forward button - url changes to page.html#products - history plug-in notices url change, calls pageload function - pageload function does something based on products I hope this makes sense. You will need to: 1) remove the inline onclick for each of your links. That overrides the history plug-in and you won't be able to work around it (cleanly). 2) make the href hash values different for each of your links. So, instead of: a href=# onclick=showHome()Home/a You'll need something more like: a href=#homeHome/a a href=#productsProducts/a I hope this helps. Brian. On Sun, Nov 23, 2008 at 10:51 PM, OhNoMrBill [EMAIL PROTECTED] wrote: Anyone have an ideal on this? On Nov 22, 8:15 pm, OhNoMrBill [EMAIL PROTECTED] wrote: I am in a real bind on this issue. Is anyone able to answer? Help would be greatly appreciated if you can!! On Nov 22, 10:50 am, OhNoMrBill [EMAIL PROTECTED] wrote: Here is the scenario I am trying to deal with currently: I have a link that looks like: a href=# onClick=$.Content_Home();Some Link/a All the url links in this site look like this...onclick overrides. What I need to do is ensure that when a user clicks back, the actual prior jQuery function is called, and not the entire page. I tried the history plugin, and can not seem to get it to pick this kind of thing up. Anyone with direct experience on this kind of thing, please chime in with some suggestions.- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
[jQuery] Re: Back Button
That makes sense; but then how do I bind the functions to the links? The functions represent a large block of black-boxed code that is an AJAX handler that pushes content into destination divs. On Nov 24, 2:52 am, Brian Cherne [EMAIL PROTECTED] wrote: Take a look at the history plug-in page code again: http://www.mikage.to/jquery/jquery_history.html A really important concept to understand is that the history plug-in (any history plug-in) is listening / watching for the URL to change. Any change you want it to make going Back you will need to let it make going Forward (and on click) as well. You basically relinquish control to the history plug-in (actually to the pageload function if you're following the example URL to the letter). It works like this: - user clicks link with an #home href - url changes to page.html#home - history plug-in notices url change, calls pageload function - pageload function does something based on home - user clicks link with an #products href - url changes to page.html#products - history plug-in notices url change, calls pageload function - pageload function does something based on products - user clicks browser's Back button - url changes to page.html#home - history plug-in notices url change, calls pageload function - pageload function does something based on home - user clicks browser's Forward button - url changes to page.html#products - history plug-in notices url change, calls pageload function - pageload function does something based on products I hope this makes sense. You will need to: 1) remove the inline onclick for each of your links. That overrides the history plug-in and you won't be able to work around it (cleanly). 2) make the href hash values different for each of your links. So, instead of: a href=# onclick=showHome()Home/a You'll need something more like: a href=#homeHome/a a href=#productsProducts/a I hope this helps. Brian. On Sun, Nov 23, 2008 at 10:51 PM, OhNoMrBill [EMAIL PROTECTED] wrote: Anyone have an ideal on this? On Nov 22, 8:15 pm, OhNoMrBill [EMAIL PROTECTED] wrote: I am in a real bind on this issue. Is anyone able to answer? Help would be greatly appreciated if you can!! On Nov 22, 10:50 am, OhNoMrBill [EMAIL PROTECTED] wrote: Here is the scenario I am trying to deal with currently: I have a link that looks like: a href=# onClick=$.Content_Home();Some Link/a All the url links in this site look like this...onclick overrides. What I need to do is ensure that when a user clicks back, the actual prior jQuery function is called, and not the entire page. I tried the history plugin, and can not seem to get it to pick this kind of thing up. Anyone with direct experience on this kind of thing, please chime in with some suggestions.- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
[jQuery] Re: Back Button
Anyone have an ideal on this? On Nov 22, 8:15 pm, OhNoMrBill [EMAIL PROTECTED] wrote: I am in a real bind on this issue. Is anyone able to answer? Help would be greatly appreciated if you can!! On Nov 22, 10:50 am, OhNoMrBill [EMAIL PROTECTED] wrote: Here is the scenario I am trying to deal with currently: I have a link that looks like: a href=# onClick=$.Content_Home();Some Link/a All the url links in this site look like this...onclick overrides. What I need to do is ensure that when a user clicks back, the actual prior jQuery function is called, and not the entire page. I tried the history plugin, and can not seem to get it to pick this kind of thing up. Anyone with direct experience on this kind of thing, please chime in with some suggestions.- Hide quoted text - - Show quoted text -
[jQuery] Back Button
Here is the scenario I am trying to deal with currently: I have a link that looks like: a href=# onClick=$.Content_Home();Some Link/a All the url links in this site look like this...onclick overrides. What I need to do is ensure that when a user clicks back, the actual prior jQuery function is called, and not the entire page. I tried the history plugin, and can not seem to get it to pick this kind of thing up. Anyone with direct experience on this kind of thing, please chime in with some suggestions.
[jQuery] Re: Back Button
I am in a real bind on this issue. Is anyone able to answer? Help would be greatly appreciated if you can!! On Nov 22, 10:50 am, OhNoMrBill [EMAIL PROTECTED] wrote: Here is the scenario I am trying to deal with currently: I have a link that looks like: a href=# onClick=$.Content_Home();Some Link/a All the url links in this site look like this...onclick overrides. What I need to do is ensure that when a user clicks back, the actual prior jQuery function is called, and not the entire page. I tried the history plugin, and can not seem to get it to pick this kind of thing up. Anyone with direct experience on this kind of thing, please chime in with some suggestions.
[jQuery] Re: HTML Partial Element Does Not Exist?!
That is a bit cryptic, what do you mean by completed? The AJAX call does successfully fire the call back for success. It is after this call back completes, that a scrubber function is called on the newly arrived div. Which, we are told is undefined. So, the question is why would a div that displays in the browser not be available by a reference such as: alert($(#MyDiv).html()); or alert($(#MyDiv).text()); On Apr 9, 9:36 pm, Hamish Campbell [EMAIL PROTECTED] wrote: Is this an ajax call? 90% of these questions seem to come down to the call not being completed. On Apr 10, 1:38 pm, OhNoMrBill [EMAIL PROTECTED] wrote: Yup, agreed. Tried that method too. Both return undefined. Any other thoughts on why the div and/or it's contents are not showing up in the DOM? On Apr 9, 4:49 pm, Wizzud [EMAIL PROTECTED] wrote: Your div does not actually contain any HTML, just text. Try ... alert($(#MyDiv).text()); On Apr 9, 8:39 pm, OhNoMrBill [EMAIL PROTECTED] wrote: I have an HTML partial coming back from a server that includes a named div (ex: div id=MyDivblah/div) When I try to run the following on it, it shows the div as empty: alert($(#MyDiv).html()); I suspect the DOM is not aware of the retuned div (though, why it displays is then a huge mystery). Can anyone clarify this for me? Maybe tell me how to tap the DOM on the shoulder with the newly returned div? Thanks much!- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
[jQuery] Re: HTML Partial Element Does Not Exist?!
Bouncing this one up. Getting kind of urgent. Can anyone tell me what the requirements are for accessing an element delivered in an HTML partial? All I am trying to do is attach an onclick to an href...after it comes down from the server. On Apr 10, 6:47 am, OhNoMrBill [EMAIL PROTECTED] wrote: That is a bit cryptic, what do you mean by completed? The AJAX call does successfully fire the call back for success. It is after this call back completes, that a scrubber function is called on the newly arrived div. Which, we are told is undefined. So, the question is why would a div that displays in the browser not be available by a reference such as: alert($(#MyDiv).html()); or alert($(#MyDiv).text()); On Apr 9, 9:36 pm, Hamish Campbell [EMAIL PROTECTED] wrote: Is this an ajax call? 90% of these questions seem to come down to the call not being completed. On Apr 10, 1:38 pm, OhNoMrBill [EMAIL PROTECTED] wrote: Yup, agreed. Tried that method too. Both return undefined. Any other thoughts on why the div and/or it's contents are not showing up in the DOM? On Apr 9, 4:49 pm, Wizzud [EMAIL PROTECTED] wrote: Your div does not actually contain any HTML, just text. Try ... alert($(#MyDiv).text()); On Apr 9, 8:39 pm, OhNoMrBill [EMAIL PROTECTED] wrote: I have an HTML partial coming back from a server that includes a named div (ex: div id=MyDivblah/div) When I try to run the following on it, it shows the div as empty: alert($(#MyDiv).html()); I suspect the DOM is not aware of the retuned div (though, why it displays is then a huge mystery). Can anyone clarify this for me? Maybe tell me how to tap the DOM on the shoulder with the newly returned div? Thanks much!- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
[jQuery] Re: HTML Partial Element Does Not Exist?!
Not stupid at all...if any one is doing that kind of question, sure it is me :) OK, so the code actually does this: 1) AJAX Request to server (get) 2) Success: ccontent is placed into div id=someid/div 3) After content is is div, a scrubber runs and replaces links. !-- this works 4) Last a second scrubber tries to replace specific links with redirect links. !-- this fails with undefined On Apr 10, 11:56 am, Wizzud [EMAIL PROTECTED] wrote: Um, I realise this is probably a stupid question but has the named DIV actually been added into the DOM at the time you do the jQuery lookup on it? (I know you've said that it displays on the page, but you don't show what is actually being done to it to get it there) On Apr 10, 6:41 pm, OhNoMrBill [EMAIL PROTECTED] wrote: Bouncing this one up. Getting kind of urgent. Can anyone tell me what the requirements are for accessing an element delivered in an HTML partial? All I am trying to do is attach an onclick to an href...after it comes down from the server. On Apr 10, 6:47 am, OhNoMrBill [EMAIL PROTECTED] wrote: That is a bit cryptic, what do you mean by completed? The AJAX call does successfully fire the call back for success. It is after this call back completes, that a scrubber function is called on the newly arrived div. Which, we are told is undefined. So, the question is why would a div that displays in the browser not be available by a reference such as: alert($(#MyDiv).html()); or alert($(#MyDiv).text()); On Apr 9, 9:36 pm, Hamish Campbell [EMAIL PROTECTED] wrote: Is this an ajax call? 90% of these questions seem to come down to the call not being completed. On Apr 10, 1:38 pm, OhNoMrBill [EMAIL PROTECTED] wrote: Yup, agreed. Tried that method too. Both return undefined. Any other thoughts on why the div and/or it's contents are not showing up in the DOM? On Apr 9, 4:49 pm, Wizzud [EMAIL PROTECTED] wrote: Your div does not actually contain any HTML, just text. Try ... alert($(#MyDiv).text()); On Apr 9, 8:39 pm, OhNoMrBill [EMAIL PROTECTED] wrote: I have an HTML partial coming back from a server that includes a named div (ex: div id=MyDivblah/div) When I try to run the following on it, it shows the div as empty: alert($(#MyDiv).html()); I suspect the DOM is not aware of the retuned div (though, why it displays is then a huge mystery). Can anyone clarify this for me? Maybe tell me how to tap the DOM on the shoulder with the newly returned div? Thanks much!- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
[jQuery] HTML Partial Element Does Not Exist?!
I have an HTML partial coming back from a server that includes a named div (ex: div id=MyDivblah/div) When I try to run the following on it, it shows the div as empty: alert($(#MyDiv).html()); I suspect the DOM is not aware of the retuned div (though, why it displays is then a huge mystery). Can anyone clarify this for me? Maybe tell me how to tap the DOM on the shoulder with the newly returned div? Thanks much!
[jQuery] Re: HTML Partial Element Does Not Exist?!
Yup, agreed. Tried that method too. Both return undefined. Any other thoughts on why the div and/or it's contents are not showing up in the DOM? On Apr 9, 4:49 pm, Wizzud [EMAIL PROTECTED] wrote: Your div does not actually contain any HTML, just text. Try ... alert($(#MyDiv).text()); On Apr 9, 8:39 pm, OhNoMrBill [EMAIL PROTECTED] wrote: I have an HTML partial coming back from a server that includes a named div (ex: div id=MyDivblah/div) When I try to run the following on it, it shows the div as empty: alert($(#MyDiv).html()); I suspect the DOM is not aware of the retuned div (though, why it displays is then a huge mystery). Can anyone clarify this for me? Maybe tell me how to tap the DOM on the shoulder with the newly returned div? Thanks much!- Hide quoted text - - Show quoted text -
[jQuery] $.each on HTML string returned from AJAX?
I am trying to run an .each on form subelements of some html returned
in an AJAX request. Like so:
var myReturnedText = some text returned from server that contains one
or more forms...;
$(form).each(
function() {
$(this).removeAttr(onsubmit);
}
);
What I am having trouble getting my head around is where to put the
reference to the original text (myReturnedText), since it is a
variable and not a DOM element.
[jQuery] Re: interface elements odd behavio in IE
Thanks for the tip...I actually caught that after opening a bug and
having it closed :)
On Apr 4, 7:40 am, Scott González [EMAIL PROTECTED] wrote:
You're unlikely to get any help with this. Interface hasn't been
supported for a very long time. You should look into jQuery UI.
On Apr 3, 1:42 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
Bumping this one back up...if any one has any input, or even an idea
of where to start, please jump in!
On Apr 2, 7:04 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
I have reduced the issue to a class named itemHeader. This class is
assigned to the sortable's handle param.
It is only this class that remains on top of the containing accordion.
panels. That class looks like:
.groupItem .itemHeader
{
line-height: 28px;
background-color: #DAFF9F;
border-top: 2px solid #B5EF59;
color: #000;
padding: 0 10px;
cursor: move;
font-weight: bold;
font-size: 16px;
height: 28px;
position: relative;
}
Anyone have any ideas on root cause here?
On Apr 2, 4:08 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
Does anytone know of the Eyecon interface components hardwire CSS z-
index in their code?
On Apr 2, 12:34 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
I am trying to implement the sortables demo (http://
interface.eyecon.ro/demos/sort.html) in an accordion. Problem is it
works fine in FF and Safari, but IE is all wigged out. IE draws the
sortables on top of everything else, instead of inside like the other
browsers do.
Anyone have any insight on this kind of thing?
Both the accordion and the sortables are from Eyecon. They are, so
far, the only elements on the page.- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
[jQuery] Re: interface elements odd behavio in IE
Bumping this one back up...if any one has any input, or even an idea
of where to start, please jump in!
On Apr 2, 7:04 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
I have reduced the issue to a class named itemHeader. This class is
assigned to the sortable's handle param.
It is only this class that remains on top of the containing accordion.
panels. That class looks like:
.groupItem .itemHeader
{
line-height: 28px;
background-color: #DAFF9F;
border-top: 2px solid #B5EF59;
color: #000;
padding: 0 10px;
cursor: move;
font-weight: bold;
font-size: 16px;
height: 28px;
position: relative;
}
Anyone have any ideas on root cause here?
On Apr 2, 4:08 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
Does anytone know of the Eyecon interface components hardwire CSS z-
index in their code?
On Apr 2, 12:34 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
I am trying to implement the sortables demo (http://
interface.eyecon.ro/demos/sort.html) in an accordion. Problem is it
works fine in FF and Safari, but IE is all wigged out. IE draws the
sortables on top of everything else, instead of inside like the other
browsers do.
Anyone have any insight on this kind of thing?
Both the accordion and the sortables are from Eyecon. They are, so
far, the only elements on the page.- Hide quoted text -
- Show quoted text -
[jQuery] interface elements odd behavio in IE
I am trying to implement the sortables demo (http:// interface.eyecon.ro/demos/sort.html) in an accordion. Problem is it works fine in FF and Safari, but IE is all wigged out. IE draws the sortables on top of everything else, instead of inside like the other browsers do. Anyone have any insight on this kind of thing? Both the accordion and the sortables are from Eyecon. They are, so far, the only elements on the page.
[jQuery] Re: interface elements odd behavio in IE
Does anytone know of the Eyecon interface components hardwire CSS z- index in their code? On Apr 2, 12:34 pm, OhNoMrBill [EMAIL PROTECTED] wrote: I am trying to implement the sortables demo (http:// interface.eyecon.ro/demos/sort.html) in an accordion. Problem is it works fine in FF and Safari, but IE is all wigged out. IE draws the sortables on top of everything else, instead of inside like the other browsers do. Anyone have any insight on this kind of thing? Both the accordion and the sortables are from Eyecon. They are, so far, the only elements on the page.
[jQuery] Re: interface elements odd behavio in IE
I have reduced the issue to a class named itemHeader. This class is
assigned to the sortable's handle param.
It is only this class that remains on top of the containing accordion.
panels. That class looks like:
.groupItem .itemHeader
{
line-height: 28px;
background-color: #DAFF9F;
border-top: 2px solid #B5EF59;
color: #000;
padding: 0 10px;
cursor: move;
font-weight: bold;
font-size: 16px;
height: 28px;
position: relative;
}
Anyone have any ideas on root cause here?
On Apr 2, 4:08 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
Does anytone know of the Eyecon interface components hardwire CSS z-
index in their code?
On Apr 2, 12:34 pm, OhNoMrBill [EMAIL PROTECTED] wrote:
I am trying to implement the sortables demo (http://
interface.eyecon.ro/demos/sort.html) in an accordion. Problem is it
works fine in FF and Safari, but IE is all wigged out. IE draws the
sortables on top of everything else, instead of inside like the other
browsers do.
Anyone have any insight on this kind of thing?
Both the accordion and the sortables are from Eyecon. They are, so
far, the only elements on the page.
