I working with AJAX for the first time and developing on a Mac. I have a controller method named add_time_request_option that responds to an AJAX call, and does this render(:layout => false) The line "render(:layout => false) renders a view called add_time_request_option that is part of a larger page. In Firefox and Safari, this works fine. However, in IE Mac, this renders ONLY the add_time_request_option - the page that should contain it disappears. Is there a way around this? Shelby
AJAX is not supported on IE Mac. Supported platforms are: IE Win 6+, Safari 1.2+, Firefox 1.0+ (more specifically Mozilla 1.6+). Thomas Am 19.07.2005 um 16:16 schrieb Shelby Westman:> I working with AJAX for the first time and developing on a Mac. I > have a controller method named add_time_request_option that responds > to an AJAX call, and does this > > render(:layout => false) > > The line "render(:layout => false) renders a view called > add_time_request_option that is part of a larger page. In Firefox and > Safari, this works fine. However, in IE Mac, this renders ONLY the > add_time_request_option - the page that should contain it disappears. > Is there a way around this? > > Shelby > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
And you should really consider your decision to provide support for Mac IE - after all, the product is effectively discontinued (no longer ships with OS X) and has been superseded by Ssfari. But if you''re in one of those sticky positions where you just *have* to support IE (client insists on using it, strange deployment matrix etc) then consider a system of ''graceful degradation'' instead. You can use things like the ''fall-through" target to target browsers that don''t support Javascript: perhaps that could be modified to deny IE access to Ajax calls (I''m guessing here). -Phil On 19 Jul 2005, at 15:44, Thomas Fuchs wrote:> AJAX is not supported on IE Mac. > > Supported platforms are: IE Win 6+, Safari 1.2+, Firefox 1.0+ (more > specifically Mozilla 1.6+). > > Thomas > > Am 19.07.2005 um 16:16 schrieb Shelby Westman: > > >> I working with AJAX for the first time and developing on a Mac. I >> have a controller method named add_time_request_option that responds >> to an AJAX call, and does this >> >> render(:layout => false) >> >> The line "render(:layout => false) renders a view called >> add_time_request_option that is part of a larger page. In Firefox >> and >> Safari, this works fine. However, in IE Mac, this renders ONLY the >> add_time_request_option - the page that should contain it disappears. >> Is there a way around this? >> >> Shelby >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > >-- Phil Powell :: (yardpartners) Hatfield House, 52-54 Stamford Street, London, SE1 9LX. w: www.yardpartners.com t: + 44 (0) 207 928 5099 f: + 44 (0) 207 928 4488 m: + 44 (0) 7811 346 731 -- This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you have received this email in error please notify the sender and delete immediately. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Yard Partners Ltd. The recipient should check this email and any attachments for the presence of viruses. Yard Partners Ltd. accepts no liability for any damage caused by any virus transmitted by this email. -- _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On 7/19/05, Phil Powell <phil-jKDN/tUcuWxMHR6vDRUiDQ@public.gmane.org> wrote:> And you should really consider your decision to provide support for Mac IE - > after all, the product is effectively discontinued (no longer ships with OS > X) and has been superseded by Ssfari. >I think you are right. Time to abandon it... Thanks, Shelby
mind you that MS disbanded the IE team for mac close to two years ago so it''s not even a worth while download anymore. (I''m not even sure if they still have it downloadable) On Jul 19, 2005, at 10:55 AM, Shelby Westman wrote:> On 7/19/05, Phil Powell <phil-jKDN/tUcuWxMHR6vDRUiDQ@public.gmane.org> wrote: > >> And you should really consider your decision to provide support >> for Mac IE - >> after all, the product is effectively discontinued (no longer >> ships with OS >> X) and has been superseded by Ssfari. >> >> > > I think you are right. Time to abandon it... Thanks, > > Shelby > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >J Brien | HybridIndie Productions | hybridindie.com | iam-QLwuMy0vUAhCl22TKe+ceQ@public.gmane.org
There are still a lot of people who use IE on the Mac. Remember that Panther originally shipped with IE (and not Safari). Not everyone has upgraded to Tiger, and those same people are the type that probably aren''t visiting Software Update. I would love to abandon this and other crappy browsers, but I don''t want to abandon potential customers. --bryce
Most people I know who have done Tiger updates in a professional setting have chosen the Upgrade or Archive and Install options over clean installs. This means that IE remains on their system and, for many, remains their browser of choice. Many of the advertising-related projects I''ve done have Mac users at about 25-30% IE lately. It could be dangerous to alienate non-GUI browser users, non-JS users, *and* users of older browsers, depending on your market. That isn''t a developer decision, though -- or shouldn''t be -- instead being in the domain of the marketing/business folks. On Jul 19, 2005, at 11:15 AM, bryce benton wrote:> There are still a lot of people who use IE on the Mac. Remember that > Panther originally shipped with IE (and not Safari). Not everyone has > upgraded to Tiger, and those same people are the type that probably > aren''t visiting Software Update. > > I would love to abandon this and other crappy browsers, but I don''t > want to abandon potential customers. > > --bryce > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
On 19 Jul 2005, at 16:15, bryce benton wrote:> There are still a lot of people who use IE on the Mac. Remember that > Panther originally shipped with IE (and not Safari). Not everyone has > upgraded to Tiger, and those same people are the type that probably > aren''t visiting Software Update.Panther shipped with Safari *and* IE, so it''s not as though those users don''t have the option to switch from IE. I understand absolutely the necessity to cater for different audiences though, which is why I normally encourage the route of graceful degradation. Where you intend to use bleeding-edge technology like Ajax though, it''s a case of having to negate older browsers from your support matrix. These old dinosaurs have to die at some point (is anyone still supporting NS4?) and we, as developers, should be active in encouraging people to upgrade to better software in an intelligent manner. -Phil _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Not to start a rant or anything (besides I think this is getting a bit off topic - not that I''m helping much) But isn''t some of the ideas behind Rails about user experience and creating a richer one at that. This is where I see the inclusion of AJAX related code. Rails - IMHO - is about both an enjoyable experience for both the developer and the user. I see graceful ways of telling the users that you are outdated and to get over the uses of legacy software, if anything is truly to evolve it will take us, the developers, to push it and to sell it to the higher-ups. We are at the edge of development here and it is our jobs to educate the consumer, they are not going to go find out about the next greatest thing on their own if they don''t know it there, right? This is the route I have chosen for my company and it has created much success and strong responses from my community. Besides, Mac users are a very small portion of the browser community and I''m allowed to say this because I am one and watch the stats on my maintained sites. On Jul 19, 2005, at 11:24 AM, Toby Boudreaux wrote:> Most people I know who have done Tiger updates in a professional > setting have chosen the Upgrade or Archive and Install options over > clean installs. This means that IE remains on their system and, for > many, remains their browser of choice. > > Many of the advertising-related projects I''ve done have Mac users > at about 25-30% IE lately. > > It could be dangerous to alienate non-GUI browser users, non-JS > users, *and* users of older browsers, depending on your market. > That isn''t a developer decision, though -- or shouldn''t be -- > instead being in the domain of the marketing/business folks._______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
I second that. One thing though, let''s not forget accessiblity. Until you''re doing highly-specialized sites or intranet apps you''ll want to have a fallback strategy (which btw, is easy to do with Rails as you can nicely reuse partials in AJAX and "normal" page rendering!). Semantic markup and CSS should be no-brainers. And, yes. We''re at the edge of development. :) Thomas Am 19.07.2005 um 17:47 schrieb J Brien:> Not to start a rant or anything (besides I think this is getting a > bit off topic - not that I''m helping much) > > But isn''t some of the ideas behind Rails about user experience and > creating a richer one at that. This is where I see the inclusion > of AJAX related code. Rails - IMHO - is about both an enjoyable > experience for both the developer and the user. I see graceful > ways of telling the users that you are outdated and to get over the > uses of legacy software, if anything is truly to evolve it will > take us, the developers, to push it and to sell it to the higher- > ups. We are at the edge of development here and it is our jobs to > educate the consumer, they are not going to go find out about the > next greatest thing on their own if they don''t know it there, right? > > This is the route I have chosen for my company and it has created > much success and strong responses from my community. Besides, Mac > users are a very small portion of the browser community and I''m > allowed to say this because I am one and watch the stats on my > maintained sites._______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails