madankgit opened a new issue, #37659:
URL: https://github.com/apache/superset/issues/37659
### Bug description
**Bug Description:**
In Apache Superset time-series charts (Line chart with Area enabled), X-axis
year labels at the chart boundaries are partially clipped. The current year
label (e.g., 2026) is not fully visible, impacting chart readability.
**Steps to Reproduce:**
1. Use a dataset containing a date column (date_value) with data spanning
multiple years (e.g., 2025–2026).
2. Create a time-series Line Chart and enable the Area option under the
Customize tab
3. Configure:
- Time column: date_value
- Time Grain: Year
4. Observe the X-axis labels
<img width="919" height="301" alt="Image"
src="https://github.com/user-attachments/assets/20309c9f-eb7f-454d-ac26-69c8b1fab484";
/>
<br><br>
**Expected Behavior**
All X-axis year labels should be fully visible and clearly readable without
truncation.
<img width="634" height="291" alt="Image"
src="https://github.com/user-attachments/assets/f7b6a1ec-0625-46fa-a13d-1744af2a6b9d";
/>
<br><br>
**Actual Behavior**
The boundary year label (e.g., 2026) on the X-axis is partially clipped and
not fully visible, while it remains correctly displayed in the tooltip.
<img width="640" height="301" alt="Image"
src="https://github.com/user-attachments/assets/3b2bb22d-3018-4c9f-a669-06cc64789737";
/>
<img width="632" height="315" alt="Image"
src="https://github.com/user-attachments/assets/dbea0aa0-a6fa-4e59-9d6e-4e5bc04aaaf3";
/>
<br><br>
**Impact**
- Users may misinterpret time ranges and trends due to unclear or missing
axis labels, affecting data analysis accuracy.
- Clean visualization of yearly patterns is not possible
- Requires dataset-level workarounds using calculated columns
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [x] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
