Jump to content

Community

Rikki

Invision Community Team
  • Content Count

    24,094
  • Joined

  • Days Won

    61

Rikki last won the day on January 19

Rikki had the most liked content!

About Rikki

  • Rank
    IPS Brit
  • Birthday 08/17/1983

Contact Methods

IPS Marketplace

  • Resources Contributor
    Total file submissions: 3

Profile Information

  • Gender
    Male
  • Location
    Lynchburg, VA :o

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Absolutely - and we did this with a compromise. Make a preview tool available for those few customers who have valid edge cases, without adding Yet Another Button in a prominent location for all our other customers. Every extra button or toggle we add to a page increases the complexity for users a little bit more, mostly unnecessarily. We try to consider all users and balance functionality with simplicity as much as we can.
  2. Honest reason it's located where it is: we do not feel it has sufficient usefulness for most sites and most users to justify giving it a more prominent location next to the submit button. We made it a customizable toolbar button so that it's available for those few edge cases where you could argue it's useful, without it being a fundamental part of the editor UI.
  3. We can't set a fixed height on images because images need to remain responsive (i.e. scaling with the browser window). For that reason, we set a width and a ratio, and calculate the height using JS. You are correct that on very slow connections, the JS can take a second or two to execute and add the placeholder, but even without lazy-loading, images would also 'jump' as the browser downloads them and inserts them into the page. This is unfortunately a trade-off, but for those on slow connections lazy-loading should ultimately be a benefit since their browser isn't having to load a bunch of images they aren't seeing yet.
  4. Each site can set their own defaults here, so it'd depend on the site you're using. This is already the case (in fact, we're looking at simplifying the process a little bit because there's too much customization, which is confusing).
  5. We actually recently added a review of notification functionality to our internal list, and this is one of the pain points that came up. We'll hopefully be able to address it in the not too distant future.
  6. I've logged a bug report for this so we can take a closer look.
  7. I've submitted a change for 4.4.4 that will disable preloading of this sound file (meaning, it'll just load on demand when it's needed, rather than on page load).
  8. I'm not sure a complete SPA approach will ever be a good fit for our platform. That said, I could imagine that we might have a collection of 'SPAs' for key workflows - e.g., going from a list of topics into a topic, replying etc. might be one seamless process. User profiles might be another. Potentially the whole ACP could be one (or maybe each section of the ACP). GitHub takes this approach and it works well.
  9. Kind of. They have similar-ish approaches. Whereas React deals exclusively with components, Vue can do components but they're optional. There are a lot of benefits to any of the modern JS frameworks though, be it React, Vue or Angular. I'm not sure if IPS5 will have the scope to move all of our JS to a new framework, but we're always keeping an eye on things and we'll make those decisions when the time comes.
  10. .ipsApp_front is also a class on the body element, so you need to remove the space (I've also moved that class to the front of the selector for clarity): body.ipsApp_front[data-pageapp="forums"][data-pagemodule="forums"][data-pagecontroller="index"] .ipsBreadcrumb { display: none !important; } An alternative way is using the data-pagelocation attribute in the same way you've used the others, since that tells you whether it's 'front' or 'admin': body[data-pagelocation="front"][data-pageapp="forums"][data-pagemodule="forums"][data-pagecontroller="index"] .ipsBreadcrumb { display: none !important; } Either of those approaches should work 🙂
  11. We haven't changed any font sizes recently. Check you haven't accidentally zoomed the page out (e.g. Cmd/Ctrl+0 on Chrome).
  12. It's a CSS selector 🙂 .ipsType_richText.ipsType_normal > p:first-child:first-letter { ... }
  13. I agree. We added it in 4.x because users were used to the position of it in 3.x, but these days I think it's probably unnecessary.
  14. That shouldn't be the case - while we only offer US-based regions, it should not be slow even from Europe. We host many European sites without issue. I'd definitely recommend submitting a ticket so we can take a look and see what's going on 🙂
  15. Personally, I don't think that's fair on the person who has quoted you. It could substantially change the meaning of their response. I think the quote needs to show what you had said at the time you were quoted.
×
×
  • Create New...