Jump to content
View in the app

A better way to browse. Learn more.

Learn more

Ehren

Invision Community Team
  • Joined

  • Last visited

  1. Yes, this is possible 🤝 Open the Page Editor, select your widget and enable the "Hide Images" option.
  2.    socceronly reacted to a post in a topic: Pages Index Cover Photo
  3.    Club VW Golf España reacted to a post in a topic: [Theme Editor] Header
  4. This should do the trick: /* Hide subforums from forum index */ .ipsBox--forumCategory .ipsSubList{ display: none; }
  5. Nope, no plans for 5.1. The main focus was performance with a slight UI polish. Design tweaks for different areas of the software will likely come in future 5.x updates, so if there’s anything in particular with the profile page that you think needs updating, feel free to post your feedback 🤝
  6. Nice one @bags_ppp The following will do the trick too. Looks like you can get started on that upgrade! @The Old Man 🎉 .ipsIconPicker__root-icon-area { display: grid; grid-auto-rows: min-content; } .ipsIconPicker__category[data-icon-category="Emoticons"] { order: -1; }
  7. Thanks for the great feedback, especially from a device combination which I haven't used myself. DeX seems like a neat feature. Glad you've been enjoying the improvements so far! 👍
  8. Will the entire page be in French, including the navigation, user panel, footer, etc? Or just the content area? If it's just the content area, you should keep the lang attribute as en-US on the <html> element, because you'll have English content in the header/footer. You could then wrap your French content on your custom pages using: <div lang="fr-FR"> </div>
  9. I actually worked on updating some of the ACP yesterday, I'm just not sure if it'll sneak into 5.1, or if it'll come in a future update. Both the frontend and backend will continue to receive UI polishes in future updates. The frontend was given priority for 5.1 since that's where a majority of your users will visit, but the backend won't be left behind. 👍 We're using the anchor positioning API so the popover will automatically stay within the viewport, and the reactions will wrap to a new line if necessary. Here's an example with 35 reactions. I don't recommend doing this, but it's possible 😇 On mobile, the swipe menu is used, so there's no chance of overflow there. Text labels are also shown incase any reaction icons are ambiguous.
  10. Invision Community 5.1 brings a wide range of improvements to the user interface, with a particular focus on performance, accessibility, and usability. We’ve modernized many of our existing components, reduced our reliance on third-party JavaScript, and made dozens of small refinements that make the overall experience feel faster and more intuitive. Here are some of the highlights. Better performancePerformance has been a major focus of 5.1. We’ve upgraded jQuery to version 4 and have removed several third-party libraries, including UnderscoreJS. Combined with the performance improvements introduced in 5.0, this has reduced the amount of JavaScript downloaded on each page by around 250KB compared to Invision Community 4. That means less code for the browser to download and process, helping communities load and respond faster while relying less on third-party libraries. Several individual components have also seen significant reductions in JavaScript. Mini profilesMini profiles have received a significant overhaul in 5.1. Previously, a mini profile could accidentally appear simply by moving your mouse over the trigger. They also presented a number of accessibility issues. In 5.1, mini profiles require a deliberate click or tap to open. They’re now fully keyboard accessible and, for the first time, they work on touch devices. On mobile, you can also use a familiar swipe gesture to dismiss the profile card. RatingsRatings have been redesigned to make them both more deliberate and significantly lighter. In 5.0, it was possible to submit a rating accidentally with an unintended tap or mouse click. In 5.1, rating options are contained within a simple dropdown that only appears after an intentional interaction. The component has also received an 80% reduction in JavaScript, making it considerably lighter. ReactionsThe reactions interface has also been modernized. Previously, the reaction menu appeared when hovering over the component, which could make the interface feel a little fragile, especially when using a mouse. In 5.1, the reaction picker is opened with an intentional click and can be navigated entirely with the keyboard. It’s also around 40% lighter in JavaScript. Native form controlsWe’ve updated a number of form components to make greater use of native browser controls. One example is the select tree. In 5.1, it uses the Popover API alongside semantic input elements. This improves its accessibility while also allowing us to reduce its JavaScript by around 75%. Password peekWe’ve also added a password peek feature to password inputs throughout the platform. A simple control lets users temporarily reveal what they’ve typed, making it easier to catch typing mistakes before submitting a form. Accessibility improvements under the hoodIn 5.1, screen readers receive more accurate information about interactive elements such as menus and dialogs. We’ve also replaced dozens of interactive links with native button elements where appropriate. These changes provide better semantics and more predictable keyboard behaviour, helping make the interface more usable for people who navigate communities without a mouse. A more polished 5.1These are just some of the changes coming in Invision Community 5.1. Alongside the improvements highlighted here, we’ve made dozens of other accessibility improvements, performance optimizations, UI refinements, and bug fixes throughout the platform. The result is an interface that is faster, more accessible, and more polished, while making better use of modern browser capabilities and native controls. We’re looking forward to getting 5.1 into your hands shortly!
  11. Invision Community 5.1 brings a wide range of improvements to the user interface, with a particular focus on performance, accessibility, and usability. We’ve modernized many of our existing components, reduced our reliance on third-party JavaScript, and made dozens of small refinements that make the overall experience feel faster and more intuitive. Here are some of the highlights. Better performancePerformance has been a major focus of 5.1. We’ve upgraded jQuery to version 4 and have removed several third-party libraries, including UnderscoreJS. Combined with the performance improvements introduced in 5.0, this has reduced the amount of JavaScript downloaded on each page by around 250KB compared to Invision Community 4. That means less code for the browser to download and process, helping communities load and respond faster while relying less on third-party libraries. Several individual components have also seen significant reductions in JavaScript. Mini profilesMini profiles have received a significant overhaul in 5.1. Previously, a mini profile could accidentally appear simply by moving your mouse over the trigger. They also presented a number of accessibility issues. In 5.1, mini profiles require a deliberate click or tap to open. They’re now fully keyboard accessible and, for the first time, they work on touch devices. On mobile, you can also use a familiar swipe gesture to dismiss the profile card. RatingsRatings have been redesigned to make them both more deliberate and significantly lighter. In 5.0, it was possible to submit a rating accidentally with an unintended tap or mouse click. In 5.1, rating options are contained within a simple dropdown that only appears after an intentional interaction. The component has also received an 80% reduction in JavaScript, making it considerably lighter. ReactionsThe reactions interface has also been modernized. Previously, the reaction menu appeared when hovering over the component, which could make the interface feel a little fragile, especially when using a mouse. In 5.1, the reaction picker is opened with an intentional click and can be navigated entirely with the keyboard. It’s also around 40% lighter in JavaScript. Native form controlsWe’ve updated a number of form components to make greater use of native browser controls. One example is the select tree. In 5.1, it uses the Popover API alongside semantic input elements. This improves its accessibility while also allowing us to reduce its JavaScript by around 75%. Password peekWe’ve also added a password peek feature to password inputs throughout the platform. A simple control lets users temporarily reveal what they’ve typed, making it easier to catch typing mistakes before submitting a form. Accessibility improvements under the hoodIn 5.1, screen readers receive more accurate information about interactive elements such as menus and dialogs. We’ve also replaced dozens of interactive links with native button elements where appropriate. These changes provide better semantics and more predictable keyboard behaviour, helping make the interface more usable for people who navigate communities without a mouse. A more polished 5.1These are just some of the changes coming in Invision Community 5.1. Alongside the improvements highlighted here, we’ve made dozens of other accessibility improvements, performance optimizations, UI refinements, and bug fixes throughout the platform. The result is an interface that is faster, more accessible, and more polished, while making better use of modern browser capabilities and native controls. We’re looking forward to getting 5.1 into your hands shortly! View full blog entry
  12. There was a missing </div> with your header ad. Luckily not a software issue. All sorted! 🤝
  13. Sounds great. You can add a background-image to your header by adding this to your Custom CSS area. Just replace the URL with your own image (you can use the Manage Resources area in your theme settings to upload images). .ipsHeader__primary{ background-image: url('https://site.com/image.jpg'); background-size: cover; background-position: 50%; }
  14. You’ll need to enable it in your group settings in that case. Admin Cpanel > Members > Groups > Select group > Edit > Group Settings > Can change layouts
  15. Yep. Users can change layouts for most applications under their User menu > Account settings > Content Preferences.
  16. If you want to merge both light and dark values into a single property, you can use the --if- variables, like so: .your-element{ background: var(--if-light, red) var(--if-dark, blue); }But otherwise the [data-ips-scheme] attribute is correct. 👍
  17. Hey Jim, Is this now working correctly in the latest v5 release? I believe we had a few bugs in an older version.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.