# Windows Mobile 2005 - RESTful Javascript Issues

**URL:** <https://www.ruby-forum.com/t/windows-mobile-2005-restful-javascript-issues/131251>\
**Category:** Rails\
**Created:** [March 7, 2008, 11:43am UTC](https://www.ruby-forum.com/t/windows-mobile-2005-restful-javascript-issues/131251 "2008-03-07T11:43:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![reynar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e99b99/32.png) [@reynar](https://www.ruby-forum.com/u/reynar)\
**Post date:** [March 7, 2008, 11:43am UTC](https://www.ruby-forum.com/t/windows-mobile-2005-restful-javascript-issues/131251/1 "2008-03-07T11:43:11Z")

</div>

Hi,

I’m developing a warehouse management app that is partly accessed via  
Windows Mobile 2005 devices. Unfortunately I’m having trouble with the  
links generated for DELETE and PUT resource requests. In generating  
the javascript to fake these HTTP methods it seems to break javascript  
compatibility with the Pocket IE browser.

As an example:

[Logout](https://www.ruby-forum.com/sessions/1)

Has anyone run up against this before and do you think there is a  
workaround? The problem is I’m tagging this system onto a main desktop  
version by way of the respond\_to do | format | … end where I’ve  
detected the browser and set it to handheld where required (similar to  
all the rails iPhone app tutorials). I think this limits what I can do  
as the server is expected POST requests at the very least and with  
hidden \_method attributes. Ideally I’d not like to have to create a  
bunch of manual routes to the same resources just for the handheld  
devices.

All thoughts much appreciated.

Andrew.

---

<div class="post-metadata">

**Author:** ![reynar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e99b99/32.png) [@reynar](https://www.ruby-forum.com/u/reynar)\
**Post date:** [March 7, 2008, 2:02pm UTC](https://www.ruby-forum.com/t/windows-mobile-2005-restful-javascript-issues/131251/2 "2008-03-07T14:02:38Z")

</div>

I’ve tracked the problem down to WM5 not supporting the  
document.createElement() method.

Is there anyway to get the link\_to helper to output the actual form to  
the page rather than generating it on the fly? I suppose I could  
rewrite the helper for mobile use?

Just wanted to check I’m not missing something obvious before I set  
out on a workaround.

On 7 Mar, 10:42, Andrew E. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)