Open Issues Need Help
View All on GitHubAI Summary: The `SubjectProcessor` class in `openlibrary/core/lists/engine.py` has become obsolete after the resolution of issue #12112. The issue proposes to safely remove this unused class as part of a code cleanup effort.
One webpage for every book ever published!
AI Summary: The advanced search page on mobile devices currently has search bars that are too wide and cause the page to overflow. The goal is to fix this overflow by applying a similar responsive pattern used on other search pages, ensuring a minimal change that only addresses the overflow issue.
One webpage for every book ever published!
AI Summary: This feature request aims to prevent inline imports specifically within the FastAPI directory of the project. The goal is to enforce this rule using a pre-commit hook, configured in pyproject.toml, to improve code quality and consistency in that specific module. This is a targeted approach to avoid broader merge conflicts.
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
AI Summary: This feature request proposes to improve the loading performance of book pages by lazy-loading history tables. Instead of loading them immediately, they will only be fetched and displayed when they scroll into the user's viewport, reducing initial page load times and blocking.
One webpage for every book ever published!
One webpage for every book ever published!
AI Summary: The focus ring around the search input field on the Search Books page is misaligned, appearing slightly offset from the input's borders. The issue requires CSS adjustments to ensure the focus outline perfectly aligns with the search field for improved visual appearance and design consistency.
One webpage for every book ever published!
One webpage for every book ever published!
AI Summary: This issue proposes migrating the `/cdn/archive.org/donate.js` and `/cdn/archive.org/athena.js` endpoints from the legacy web.py framework to FastAPI. The goal is to replicate the existing functionality, including fetching JavaScript files from archive.org and setting specific cache headers, within the new FastAPI structure as part of an ongoing migration effort.
One webpage for every book ever published!
One webpage for every book ever published!
AI Summary: This feature request proposes adding a SQL linter, such as `sqlfluff`, to the pre-commit hooks. The goal is to prevent syntax errors (like missing semicolons) in `.sql` files, which have previously caused initialization failures for new developers, though existing developers were unaffected due to container caching.
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
AI Summary: The 'Privacy & Content Moderation Settings' page incorrectly sets the `checked` attribute for radio buttons, resulting in an invalid HTML value like `checked=""checked""` instead of a simple boolean `checked`. This issue can be resolved by modifying the `selected` function in the `privacy.html` template to correctly apply the `checked` attribute.
One webpage for every book ever published!
AI Summary: On the "Privacy & Content Moderation Settings" page, clicking the label associated with a radio button does not select that radio button. This is likely due to a mismatch between the `for` attribute of the `<label>` element and the `id` attribute of its corresponding `<input type="radio">` element.
One webpage for every book ever published!
One webpage for every book ever published!
AI Summary: Users can repeatedly click download buttons for patron exports, leading to multiple downloads because the UI doesn't indicate an ongoing download or disable the button. The proposed solution involves disabling the button and changing its text to "Downloading..." on click, then reverting it once the download is complete.
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
One webpage for every book ever published!
AI Summary: The task involves improving the visual consistency of card components in the Open Library website. Specifically, it requires updating the styling of the "Community List" label to match the styling of other labels, potentially by replacing the user avatar with the Open Library logo while maintaining existing classes and font styles.
One webpage for every book ever published!
AI Summary: Debug and fix a CSS padding issue affecting the 'Join Waitlist' button on the Open Library homepage. This involves inspecting the provided HTML and CSS, identifying the cause of the missing padding, and implementing a fix that ensures proper visual presentation of the button.
One webpage for every book ever published!
AI Summary: The task involves removing several unused functions (`fetchPartials`, `updateReadingLog`, `removeFromList`, `addToList`, `createNewList`, and potentially `post`) from the `ListService.js` file within the Open Library project. This is a code cleanup task aimed at improving maintainability.
One webpage for every book ever published!