<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Removes the arbitrary bio limit
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Add support for misskey-flavored markdown color definitions. E.g.
`$[fg.color=f00 bg.color=00ff00 red on green]`.
Fix single new lines after block quotes being block-quoted.
Hardened html parsing in standard input box, should no longer randomly
delete text in arrow brackets (unless valid, properly closed, legal
html).
Fix matrix.to links getting arrow brackets inserted when editing
messages.
Fix mentions breaking after editing messages with mentions. Fixes#858
Fix emojis not rendering in reply chips.
Fixed starting lists at arbitrary numbers and list markers extending off
screen with long numbers.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [x] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
Tests were fully AI generated. AI helped with some of the regex which I
then verified and tested.
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Fixes tablet layout sidebar taking up the full screen
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Attempts to credit everyone who contributed to a PR instead of just the
pr opener.
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
I've fixed many issues with the image viewer, while also adding some
intuitive functionality.
Fixes:
- Inline styles that aren't changed dynamically have been moved to the
CSS.
- The Zoom % pill no longer changes size except for manual zoom over
500%. This prevents the +/- buttons from moving as they are being
clicked.
- Transitions are now disabled for manual panning to improve
responsiveness.
- Images are now scaled independently of browser dimensions. This means
that 100% zoom will always refer to the image's native size, and zoomed
images will be rendered at full quality. (Previously, a small browser
window would shrink the base image such that zooming in would make it
visibly blurry.)
- Pinch gestures generally did not work before (as their detection was
usually overridden by the double tap detection, since pinching
inherently involves using two fingers); This should be fixed. (Waiting
for a deployment to test properly!)
- The double tap gesture will no longer be triggered by extremely fast
double taps, to prevent accidental triggers.
Changes:
- The Zoom % pill now allows entering a custom zoom value, rather than
resetting to 100% zoom on click.
- Related to the previous change, there is now a View Original Size
button (with a photo icon) that only appears when you aren't already at
100% zoom.
- With the image scaling changes, I *have* reasonably kept the original
behavior, with alterations to stay intuitive: Until an image being
viewed is manually panned or zoomed (or the view is reset), it is
automatically scaled to fit the container it's in.
- Related to the previous change, there is a Reset View button (with a
refresh icon) that only appears when you have manually panned or zoomed
away from the initial rendered position.
- The default rendering style for images is now `pixelated`; this
preserves detail for smaller images, especially pixel art, and
*shouldn't* be relevant for larger images, but it's a change I'm willing
to revert.
Known issues:
- The Reset View button doesn't animate the transition back to the
original view, but the View Original Size button does. I could not
figure out how to get this to work properly.
- Some functionalities/changes I'd make aren't possible without
project-wide reworks:
- Some of the buttons' functionalities would be much clearer with
tooltips, but *no* components use browser-level tooltips and I don't
feel confident adding the pop-up tooltips used in the sidebar.
- I would add a border to the Download button for better contrast, but
the only "Primary"-colored button I've seen with borders is the Mark All
As Read button, so changing that would require a broader scope.
- Some of these changes may need to be put into the PDF viewer as well,
or perhaps we should combine those two things at some point?
- It feels disingenuous for me to bundle a bug fix with added
functionality, but the process of fixing these bugs led to gaps that
needed to be filled; If necessary, we can try to separate this into two
PRs, but I assume the functionality will be appreciated already.
- This needs a changeset, but I'm not sure exactly how much of this will
make sense to put into it, since it's a fairly big change.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
### AI disclosure:
- [x] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
I used AI to help wire gestures correctly and deal with correctly
selectively disabling animation transitions.
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Adds a comment and info to changeset about original Cinny source, which
was missing outside of the corresponding PR description.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
Add settings for rooms icons showing for every space with the default
leaving it up to the general setting for icons showing, and the rest
overriding it:
<img width="823" height="697" alt="image"
src="https://github.com/user-attachments/assets/7dd3255d-e483-4545-99fc-e14066a867a5"
/>
For the Room currently it will be present inside of the
<img width="810" height="695" alt="image"
src="https://github.com/user-attachments/assets/061d1c84-a1f6-4e3e-a216-77db96ef4063"
/>
It also adds styling to the RoomCard using the banner in preparation of
maybe when it might happen that the associated MSC gets merged into the
spec (as it stands it only works with rooms you are already a member of
as it is stored as a regular state event)
<img width="993" height="1064" alt="image"
src="https://github.com/user-attachments/assets/ed6ac35d-fa28-4292-a1bb-f4fd883a2035"
/>
And it also increases the size of the Vertical resizer bar as they are
the ones that are possible to be seen on mobile and it helps with
gripping them, and separated them into classes better so it might be
more easily changeable with a tweak if so desired.
<img width="536" height="535" alt="image"
src="https://github.com/user-attachments/assets/69661a59-9727-4ced-b165-27afb29c751a"
/>
Lastly it fixes the banner buttons previously being enabled when the
user is missing the permissions to edit the room banner
Fixes #
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
Caine (the AI from TADC) gave me swappable parts and trapped me into a
circus if that counts as assistance!
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Ported over from cinny with minor changes to avoid the linter disable
next line comment they use
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Fixes#835
Centers the load indicators properly so they dont appear in the top
right.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Untested fix for #834 , just adds an additional check to make sure that
we aren't trying to concat on an empty array which I think is likely
what caused the crash.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Fixes the random \<> and links being too aggressive with parsing leading
to the entire markdown structure being seen as part of it and fixes
editing messages with suppressed links not remaining suppressed.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [x] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
Tests were AI generated.