fuzzy

About me: <code>,[code],'code'=>'code',{'code','code'}</code>
Location:

Send private message

You must be logged in to send a private message.

Friends

No friends yet.

Group membership

Activity

  • fuzzy replied on the discussion topic Progressive Enhancement JavaScript Strategy?
    Hi Jerome, For myself I always develop without JS first for accessibilty. then use Javascript as a feature, this ensures that no matter what the site will always function. The main case where this is an issue in elgg is comments, if you... view reply
  • fuzzy replied on the discussion topic Progressive Enhancement JavaScript Strategy?
    Well, it's unfortunate nobody wants to discuss this topic. I'v fixed it before by over riding most of the default JS in my themes. It wasn't very difficult to fix, but it makes upgrading more difficult than it needs to be.  It... view reply
  • fuzzy added a new discussion topic Progressive Enhancement JavaScript Strategy? in the group Plugin Development
    Core functionality should not be JavaScript dependent.
    • Well, it's unfortunate nobody wants to discuss this topic. I'v fixed it before by over riding most of the default JS in my themes. It wasn't very difficult to fix, but it makes upgrading more difficult than it needs to be.  It is a huge flaw in the core platform that deviates from very basic best practice standards.

    • If you have any suggestions on how to make core less dependent on JS, feel free to submit a Pull Request to Elgg https://github.com/Elgg/Elgg with your changes.

      Why would depending on JS be a problem? If it's an accessibility issue, we try to make most of core work just fine.

      Maybe you have other suggestions? Those are always welcome. Maybe the best suggestions could be reported https://github.com/Elgg/Elgg/issues

    • Hi Jerome,

      For myself I always develop without JS first for accessibilty. then use Javascript as a feature, this ensures that no matter what the site will always function. The main case where this is an issue in elgg is comments, if you disable JS there is no way for users to comment, most other instances are in individual plugins where it can be corrected in the plugin, I do recal many years ago fixing this issue, but today that code is probably stale if I could even find it again. I posted this mostly to guage if there is support for a project like this. Accessibility is so often forgotten in modern web, but in this case it impeeds normal functionality. I'll keep checking if more support arives, other wise I'll just keep it on my when I get to it list.  Thanks Jerome.

  • fuzzy replied on the discussion topic adding setting to the user settings page.
    The docs make it seem all auto-magical and unclear, somewhere it implied you dont need any kind of action handler, like the plugin setting, another place it implies there should be an action/plugin/handler. What a mess.... This section of the... view reply
  • fuzzy replied on the discussion topic adding setting to the user settings page.
    Thanks Nicolai, knowing what I should expect helped a lot.  The docs dont seem to mention all this either:      public function init() {         // Additional initialization if needed    ... view reply
  • fuzzy replied on the discussion topic adding setting to the user settings page.
    Yeah the field is in the correct location. I should expect it to show on the settings page? view reply
  • fuzzy replied on the discussion topic adding setting to the user settings page.
    Do I actually need the user here?  yeah that was dumb comment on my part.. So frusterated... I'v cleared the cache a million times, let me try manually deleting the cache dir. I'm affraid of upgrade It has blown me out to may... view reply
  • fuzzy replied on the discussion topic adding setting to the user settings page.
    I had claude search the web, the docs, the core, and it couldnot figure it out either. view reply