1. 28 Jun, 2022 2 commits
  2. 27 Jun, 2022 3 commits
  3. 25 Jun, 2022 1 commit
  4. 23 Jun, 2022 2 commits
  5. 20 Jun, 2022 1 commit
  6. 19 Jun, 2022 1 commit
  7. 17 Jun, 2022 1 commit
    • Ambroise Rosset's avatar
      Fix a mistake in commit 1b2c616c · 5ea53b2d
      Ambroise Rosset authored and Jan Grulich's avatar Jan Grulich committed
      When I have provided the commit 1b2c616c to add the possibility to tune
      the useragent, I have forgoted to initiliaze the UserAgent field with
      the current value present in configuration file.
      
      This commit only fix this issue
      5ea53b2d
  8. 13 Jun, 2022 1 commit
  9. 10 Jun, 2022 1 commit
  10. 07 Jun, 2022 1 commit
  11. 05 Jun, 2022 1 commit
  12. 31 May, 2022 1 commit
  13. 29 May, 2022 1 commit
  14. 28 May, 2022 1 commit
  15. 27 May, 2022 1 commit
  16. 25 May, 2022 1 commit
  17. 22 May, 2022 2 commits
  18. 19 May, 2022 3 commits
  19. 18 May, 2022 1 commit
  20. 17 May, 2022 1 commit
  21. 16 May, 2022 2 commits
  22. 15 May, 2022 1 commit
  23. 01 May, 2022 1 commit
  24. 24 Apr, 2022 1 commit
  25. 23 Apr, 2022 1 commit
  26. 19 Apr, 2022 1 commit
  27. 16 Apr, 2022 1 commit
  28. 12 Apr, 2022 1 commit
  29. 11 Apr, 2022 1 commit
  30. 05 Apr, 2022 1 commit
  31. 04 Apr, 2022 1 commit
    • Arjen Hiemstra's avatar
      Don't use forceActiveFocus to focus the applet toolbar · 974fe05e
      Arjen Hiemstra authored and Nate Graham's avatar Nate Graham committed
      Generally, using forceActiveFocus is a bad thing since it indicates
      something is wrong in how focus is setup. It is also unnecessary here.
      PlasmoidHeading is a focus scope which means we can set whatever default
      focus we want inside it and then simply focus the heading to get our
      desired behaviour.
      
      In addition, we now use Plasmoid.expanded to retrigger the focus binding
      so that it is properly reset on re-showing the applet.
      974fe05e
  32. 31 Mar, 2022 1 commit
    • Nate Graham's avatar
      applet: port away from contextMenu and use contextualActionsModel · d13233b0
      Nate Graham authored
      With changes to ExpandableListItem, we can now define both contextual
      actions and a custom content view. This means we can put the actions
      that are currently in the context menu in the contextual actions list
      instead, so they will be displayed in the expanded view above the custom
      content.
      
      This yields several benefits:
      - Makes these items more consistent with other expandable list items in
        other widgets
      - Removes the use of a context menu, which goes against the purpose of
        this component (to be fully usable with only left-clicks or touches)
      - Removes a PlasmaComponents2 import
      d13233b0