Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Search results

  1. dstromberg

    HTML & CSS Sometimes ng-change fires, sometimes it doesn't

    Using ng-click instead of ng-change solved the problem. Thanks to Zachary Askins for that suggestion.
  2. dstromberg

    HTML & CSS Sometimes ng-change fires, sometimes it doesn't

    This does appear to matter, because if I add it to the happy-path, the errors commence immediately, instead of waiting until when the "you didn't really want to do that" case kicks in.
  3. dstromberg

    Hey

    Hi. I'm mostly into Python+Cython+Bash+C, but I've been studying HTML/CSS/AngularJS/React/Javascript/TypeScript for work lately, and this appears to be a good resource for most of those - perhaps especially the web frontend technologies. Thanks.
  4. dstromberg

    HTML & CSS Sometimes ng-change fires, sometimes it doesn't

    Oh! It probably matters that I'm using AngularJS!
  5. dstromberg

    Python Beginner Question - Would Python be the correct choice to build a bot for eBay?

    If it's not a violation of the ToS on E-Bay, check out BeautifulSoup and/or lxml for your screenscraping in Python. Last I heard, these were the two most common modules for such things in Python.
  6. dstromberg

    HTML & CSS Sometimes ng-change fires, sometimes it doesn't

    In case it matters, I'm sometimes changing the state of the button from Javascript, using: function sendCheckboxClick(which, set_to) { let checkbox_button = document.getElementById(which); let bool_checkbox_button = !! set_to; console.log(`fred 5: Setting checkbox button to...
  7. dstromberg

    HTML & CSS Sometimes ng-change fires, sometimes it doesn't

    Hello people. I'm trying to convert two radio-buttons to a single checkbox (with some vestiges of pure CSS checkbox I suspect), and having difficulty that I'm pretty sure is due to my lack of familiarity with CSS. In short, sometimes when I click the checkbox, it runs my ng-change, and...
  8. dstromberg

    Resetting a radio button to defaults?

    It turned out someone had added some "important" settings, which was strongly deterring my local settings. I got around that by adding my own "important" settings on those input elements, to override the broader/older ones.
  9. dstromberg

    Resetting a radio button to defaults?

    Continued thanks for taking an interest in this. I think a small test project would do the buttons well, but I'm working in a large project which has CSS coming from all over the place. I'm thinking some snippet of CSS somewhere is changing the look of the radio buttons. Rather than track...
  10. dstromberg

    Resetting a radio button to defaults?

    Thanks for the response. I changed the style= to a class=, and commented out the all:initial; Now I have: /* .un_preserve_radio input[type="radio"] { */ .un_preserve_radio { /* opacity: 1; ** position: fixed; ** width: 100%; ** -webkit-appearance: radio; ** -moz-appearance: radio...
  11. dstromberg

    Resetting a radio button to defaults?

    Hello people. I'm attempting to add a few radio buttons to a large HTML+CSS+Javascript (and Python on the backend) project. Something, somewhere in the stack is changing radio buttons to be just their lablels, and no actual visible circles. In factd, they aren't just invisible: if I click...
  12. dstromberg

    Button that won't change status until validation completes? Or that changes, but changes back if validation fails?

    I was able to disable the button with: Preserve Build<br /> <div ng-if="!vm.updatingStatus" class="onoffswitch onoffswitch-build-preserve"> <input type="checkbox" id="onoffswitch-build-preserve" name="onoffswitch-build-preserve" class="onoffswitch-checkbox"...
  13. dstromberg

    Button that won't change status until validation completes? Or that changes, but changes back if validation fails?

    Wow, it looks like this code (which is being rewritten) is using AngularJS. So I may have been closer before: ng-disabled="true"
  14. dstromberg

    Button that won't change status until validation completes? Or that changes, but changes back if validation fails?

    Hi Josiah. Thanks for your response. I'm hoping I can replace [disabled]="true" with something like [disabled]="should_be_disablable", where should_be_disablable would be in Javascript. But that might come later, because right now just using the hardcoded constant true isn't disabling the...
  15. dstromberg

    Button that won't change status until validation completes? Or that changes, but changes back if validation fails?

    I also tried: <div ng-if="!vm.updatingStatus" class="onoffswitch onoffswitch-build-preserve"> <input type="checkbox" id="onoffswitch-build-preserve" name="onoffswitch-build-preserve" class="onoffswitch-checkbox" ng-change="vm.UpdatePreserveStatus()" [disabled]="true"...
  16. dstromberg

    Button that won't change status until validation completes? Or that changes, but changes back if validation fails?

    As a test, I tried: Preserve Build<br /> <div ng-if="!vm.updatingStatus" class="onoffswitch onoffswitch-build-preserve"> <input type="checkbox" id="onoffswitch-build-preserve" name="onoffswitch-build-preserve" class="onoffswitch-checkbox" ng-change="vm.UpdatePreserveStatus()"...
  17. dstromberg

    Button that won't change status until validation completes? Or that changes, but changes back if validation fails?

    This seems to be close to what I might want to do: https://www.dofactory.com/html/button/disabled#:~:text=The%20disabled%20attribute%20on%20a,grayed%20out%20and%20is%20unusable. ...except I would need a tooltip/hover text, and I want the button disabled or not disabled on page load as well as...
  18. dstromberg

    Button that won't change status until validation completes? Or that changes, but changes back if validation fails?

    Hello people. I currently have a (I think) pure CSS button that toggles between "PRESERVED" and "NOT PRESERVED". That's been good enough 'til now, even though infrequently the button will change but the underlying state doesn't, resulting in a button that has the wrong value (IOW, "PRESERVED"...
Back
Top Bottom