I looked at the code and it seems that readAttribute has some extra
plumbing for IE but other than that it works basically as you would
expect.
On May 19, 5:16 pm, patrick patrick99...@gmail.com wrote:
Hi,
I was looking over the API docs, and saw readAttribute, and thought to
myself: I have
I looked at the code and it seems that readAttribute has some extra
plumbing for IE but other than that it works basically as you would
expect.
Yes, but my question was, is it safe for me to be doing x.id,
x.style ?
Or is it recommended to use readAttribute to get those values?
-patrick
--
Hi,
You can file documentation tickets here:
https://prototype.lighthouseapp.com/projects/42103/home
I'm a bit surprised to find that `Selector` is documented. I'd
probably stick to the higher-level interfaces -- `$$`,
`Element#select`, `Element#down`, etc.
--
T.J. Crowder
Independent Software
Yes, but my question was, is it safe for me to be doing x.id,
x.style ?
For *reflected* attributes like `id` and `className`, and for `style`
which isn't really an attribute (although its values are drawn from an
attribute, they're parsed), yes. Those are consistent cross-browser.
(With regard
I've a little problem with the Effect.SlideDown within IE7. Some
pseudo code
div id=x
ul
lia href=/link-1link 1a//li
lia href=/link-2link 2a//li
lia href=/link-3link 3a//li
/ul
/div
I've a background image at the div. When starting te effect
Effect.SlideDown('x'). The
Hey!
Mmmhhh... Currently I am thinking of how you made your script in order
to make a field editable, particularly the way you use
element.observe. The information you found is important but if you
make your script driving Prototype.js only when needed, logically, it
shouldn't be any problem.
I am having a hell of a time solving a problem in my application due
to the fact that page reloads do not seem to set input values
properly... I don't understand this at all, and am hoping someone
here can provide some insight and hopefully a solution.
If I have static html that does:
input
This is due to how browsers will save form state between page refreshes.
If you want to reset form values between refreshes, manually set the value
on page load with javascript in a dom:loaded block
But if it's just a hidden input you're worried about... the chances of
somebody fiddling with the
Patrick,
I think this is Firefox being helpful to the end user. Does this still
happen if you refresh programmatically in JavaScript?
--
Jonathan Rosenberg
Founder Executive Director, Tabby's Place
http://www.tabbysplace.org/
-Original Message-
From:
Yeah, it was not happening in Safari... And I just got it solved.
This is a rails application, so I did:
and that fixed it...
response.headers[Cache-Control] = no-cache, no-store, max-
age=0, must-revalidate
response.headers[Pragma] = no-cache
response.headers[Expires] = Fri, 01 Jan
Excellent. I wasn't aware of the documentation ticket site. I filed a
new ticket.
On May 20, 12:01 am, T.J. Crowder t...@crowdersoftware.com wrote:
Hi,
You can file documentation tickets
here:https://prototype.lighthouseapp.com/projects/42103/home
I'm a bit surprised to find that
I get an error event is not defined... test.js Line:7 when clicking
the list items inside the orange box at
http://zark.skagos.com.au/prototype_ff3_ubuntu_test
The code works in all my other browsers including Chrome/Ubuntu.
I thought the lowercase 'e' on event might have been the issue, but if
Hi,
It's best to actually paste in the code you're having trouble with;
for obvious reasons, a lot of people won't follow links, and in any
case, it's just a few lines of code.
The test.js code is:
* * * *
Event.observe(window, 'load', function() {
$('zarks').observe('click', function(e) {
13 matches
Mail list logo
