fearphage

Perhaps the title of the thread should be changed to "WebUI v0.31x" then?

Since 0.310 is dead now (long live 0.315), can we start a new thread?

bugs.utorrent.com redirected to utbugs.leetwebhosting.com which is down so I will make my bug report here. Just as I reported in February, the same mistake was made: .insertRule('cssRule { ... };' You are attempting to insert invalid css using insertRule. Following the spec, Safari and Opera throw a SYNTAX_ERR exception when the rule has a syntax error or is otherwise unparsable. This is on line 999 of the prettified stable.js. To find it in the compressed version, just search for };' and remove the semicolon. Here is a fixed version that works in Safari and Opera. Keep in mind it is 1 character different from the original. In stable.js, the 20,882nd character (a semicolon) is removed. Again I would like to offer my services in the javascript department. I see a lot of room for improvement and optimization.

So 2 years to work on basic features? Is Directrix volunteering to make the front end? I wish I had an assignment that I got paid for that I could stretch out for 2 years. Spoken like a true non-web dev

Nothing major. Just ie6, opera, and safari support (by default). I've fixed the last 2 myself. If I had the time, I'd fix ie as well. Keep in mind as old as IE6 is and as much as people seem to hate it, it still consumes a larger market share than IE7. Sources: http://www.webreference.com/stats/browser.html http://www.upsdell.com/BrowserNews/stat.htm http://www.w3schools.com/browsers/browsers_stats.asp Seems like support beyond FF2 and IE7 have been needed for a while. Those seem like important things to release for... maybe I'm just weird. With 2 years of work on a front end, he has raised the bar on my expectations. I hope SVG graphs are a part of it.... maybe even a 3D interface.

2 years on a front end? Perhaps it is time to search for replacements... I would assume he has a score of other duties that don't take 2 years each, correct? Was he hospitalized during this time period? Is he blind or otherwise handicapped? Are they hiring for his position?

2 years of development on a client-side interface... something that can't really be closed source. Wow. That is insane. I wonder why the devs didn't throw this on google code or sourceforge years ago. Anyone know? You seem to know what's going on and perhaps know the devs. If this is the case, let them know if they need help, i would like to volunteer my services. I can't imagine spending years on a front end alone... a website to be exact.

I know that you (devs) do. I was referring to a place to gather all the community patches.

Is there any reason the webui is not hosted at googlecode or some other central repository? I have seen and applied multiple fixes and improvements. It would be nice for them to gather in a central location. Would anyone (mods) be against the idea? Alternatively the updated version seems to be taking quite a while. Are they in need of assistance? I would like to offer my services. Especially in cross-browser compliance and not relying on browser-detection.

There are versions working in ff3, opera, and safari listed here: http://forum.utorrent.com/viewtopic.php?pid=289488#p289488

Seems the link above was throwing 403 errors. Here is a copy of the same webui that is made to work in Opera and Safari with 3 little fixes. http://storage.fearphage.com/.tmp/webui.zip

I did notice that it crashed from the massive innerHTML assignment. There are ways around that. For instance, you could take that html (well the correctly formed version of that html in content.js) and parse it into a document fragment and append that to the appropriate node. IE in general does all sorts of weird things. Could you be more specific? I am asking because I wouldn't mind attempting to overcome these issues if possible.

@ultima: are there particular reasons IE6 isn't supported or is it merely a hassle to support it? From a quick glance at the source I didn't see anything in particular. Could you possibly elaborate on this? Also the string of html in content.js is malformed (tags do not close in the order they are opened)

I fixed it. The code that breaks Opera and Safari is a few non-standard things. StyleSheet.href returns null in standards compliant browsers for inline stylesheets. if (!document.styleSheets[n].href || (document.styleSheets[n].href.indexOf("style.css") == -1)) { When rules are added to the stylesheet, they are in the wrong format. "selectorText { ... };" -- The semi-colon throws a syntax error in Opera. Here's a fixed copy: http://files.myopera.com/fearphage/transport/webui.zip The only reason to download this is for it to work in Opera or Safari. All 3 fixes are in stable.js (2 of the first and 1 of the second). There are other small fixes and changes that could be made but aren't requires. @devs: Besides the HUGE innerHTML assignment that crashes ie6, is there anything else that makes it unsopported? Is there a reason content.js is not hardcoded into index.html?