Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

webOS dies. Again

Name: Anonymous 2012-06-05 9:38

m.zdnet.com/blog/mobile-news/rip-webos-again-and-for-good-this-time/7980

Name: Anonymous 2012-06-05 9:58

Nobody cares. Again.

Name: Anonymous 2012-06-05 13:42

>>2
that's sad

Name: Anonymous 2012-06-05 14:39

>>2
Well...I care and I personally think that webos has a lot of potential...

Name: Anonymous 2012-06-05 16:17

>>1
hackéame los webos

Name: Anonymous 2012-06-05 16:18

I think that the WebOS vision is correct. If the Palm executives had done their work right, it would be a major platform by now, all based on Javascript, CSS and HTML5. Isn't that beautiful?

Name: Anonymous 2012-06-05 16:40

>>6
Le What?

Name: Anonymous 2012-06-05 17:21

>>7
Le yes
www.weboshelp.net/getting-started-with-webos/70-beginner-webos-mojo-tutorial

Name: Anonymous 2012-06-05 17:37

they might open source webOS, isnt that good news?

Name: Anonymous 2012-06-05 18:30

>>6
HTML5 a shit

Name: Anonymous 2012-06-05 18:32

CHECK EM

Name: Anonymous 2012-06-05 18:39

>>11

nice dubs crazy bro

Name: Anonymous 2012-06-05 18:40

I know this was posted a while ago, but in case anyone is searching for an answer and really wants to use a button element instead of an input element...

You can not use .attr('value') or .val() with a button in IE. IE reports both the .val() and .attr("value") as being the text label (content) of the button element instead of the actual value of the value attribute.

You can work around it by temporarily removing the button's label:

var getButtonValue = function($button) { var label = $button.text(); $button.text(''); var buttonValue = $button.val();
 $button.text(label);
 return buttonValue;
}

Name: Anonymous 2012-06-05 18:45

3 down vote
   

So this is way late, but I've discovered an answer, in case it becomes useful to anyone who comes across this thread.

Changes in value to hidden elements don't automatically fire the .change() event. So, wherever it is that you're setting that value, you also have to tell jQuery to trigger it.

function setUserID(myValue) {
     $('#userid').val(myValue)
                 .trigger('change');
}

Once that's the case,

$('#userid').change(function(){
      //fire yo

Name: Anonymous 2012-06-05 18:45

3 down vote
   

So this is way late, but I've discovered an answer, in case it becomes useful to anyone who comes across this thread.

Changes in value to hidden elements don't automatically fire the .change() event. So, wherever it is that you're setting that value, you also have to tell jQuery to trigger it.

function setUserID(myValue) {
     $('#userid').val(myValue)
                 .trigger('change');
}

Once that's the case,

$('#userid').change(function(){
      //fire yo

Name: Anonymous 2012-06-05 18:45

3 down vote
   

So this is way late, but I've discovered an answer, in case it becomes useful to anyone who comes across this thread.

Changes in value to hidden elements don't automatically fire the .change() event. So, wherever it is that you're setting that value, you also have to tell jQuery to trigger it.

function setUserID(myValue) {
     $('#userid').val(myValue)
                 .trigger('change');
}

Once that's the case,

$('#userid').change(function(){
      //fire yo

Name: Anonymous 2012-06-05 18:46

3 down vote
   

So this is way late, but I've discovered an answer, in case it becomes useful to anyone who comes across this thread.

Changes in value to hidden elements don't automatically fire the .change() event. So, wherever it is that you're setting that value, you also have to tell jQuery to trigger it.

function setUserID(myValue) {
     $('#userid').val(myValue)
                 .trigger('change');
}

Once that's the case,

$('#userid').change(function(){
      //fire yo

Name: Anonymous 2012-06-05 18:46

3 down vote
   

So this is way late, but I've discovered an answer, in case it becomes useful to anyone who comes across this thread.

Changes in value to hidden elements don't automatically fire the .change() event. So, wherever it is that you're setting that value, you also have to tell jQuery to trigger it.

function setUserID(myValue) {
 $('#userid').val(myValue)
 .trigger('change');
}

Once that's the case,

$('#userid').change(function(){
 //fire yo

Name: interesting 2012-06-05 18:47

3 down vote
   

So this is way late, but I've discovered an answer, in case it becomes useful to anyone who comes across this thread.

Changes in value to hidden elements don't automatically fire the .change() event. So, wherever it is that you're setting that value, you also have to tell jQuery to trigger it.

function setUserID(myValue) {
 $('#userid').val(myValue)
 .trigger('change');
}

Once that's the case,

$('#userid').change(function(){
 //fire yo

Name: Anonymous 2012-06-05 23:32

RIP MY HUEVOS

Name: Anonymous 2012-06-06 0:17

>>16
uses jquery

pls go

Name: Anonymous 2012-06-06 2:30

<--- check em
Don't change these.
Name: Email:
Entire Thread Thread List
All trademarks and copyrights on this site are owned by their respective parties. All comments and posts are the responsibility of their own posters.
- Tinychan + 2ch Mode -