Skip to main content

Recently a user ran into an issue where they can’t highlight any text within the Skuid page. I have a very similar Skuid page that works just fine, but this particular Skuid page won’t allow anyone to highlight any text in every browser I’ve tried. I even tried to clone the page, but had the same issue. The only thing I can see is this error when I do CTRL-J in Chrome Unrecognized Content-Security-Policy directive ‘reflected-xss’. However, I can’t find anything online that relates this to my problem. Has anybody else run into this? Or have any troubleshooting ideas? Thank you

Hi Korey, I am still able to see this problem in our latest version 11.2.9 so this has not yet been fixed, but is currently being tracked by our engineers. Feel free to “Me Too” this post to help bump the priority of this issue. Also, I was able to replicate the remaining interactions tags when it is inside of a sliding panel. Are you seeing the tags anywhere else?


Korey, another workaround would be to edit the XML of your page, locate the rogue tag or tags that do not actually contain any interactions and remove them from your XML. Save the page and you should then be able to highlight text on a touch device.


Khamla,


For some reason my post from yesterday disappeared (not sure what happened) so I’ll post this again:


I looked through all my pages and found 5 pages where it shows up. It appears to show up consistently when I change the page style or use a wrapper to change the style:


Example 1


<styles>
<styleitem type="background" bgtype="none"/>
</styles>
<interactions/>

Example 2


<styles>
<styleitem type="background" bgtype="color">
<styles>
<styleitem property="background-color" value="#393737"/>
</styles>
</styleitem>
<styleitem type="border"/>
<styleitem type="size"/>
</styles>


Example 3









So, how would you like me to proceed? I can obviously remove the interactions tags on these pages, and see if it’s resolved, but would you like me to try adding specific components and see if the interactions tags fix themselves?


I just want to make sure I’m testing this in a useful manner before I started changing things.


Thanks!


I removed all the in my production skuid pages, and it’s still causing the same issue. Is there any update on this issue? This is frustrating the few users who don’t have an easy way to disable the touch screen on their laptop.


Just an additional bit of details: I removed the tags on all my pages, but it looks like it only resolved it for the pages where the queue component isn’t used. I have a queue component on one of my pages (which has interaction tags for clicking on it) and it’s still exhibiting the original problem.


Can you elaborate on your problem Korey? Are your users having trouble highlighting the text inside of a queue component?


So no, I don’t expect them to be able to highlight text inside a queue component.


Basically the issue is this:


CaseDetails page - Highlight works fine now that I removed all


CaseHome page - loads a queue component, and loads CaseDetails as a page include. If you use CaseHome, you cannot select text on any CaseDetails fields.


I’ve removed all tags I could find, but CaseHome has some like this:


<interactions>
<interaction type="tap">
<action type="requeryModel" model="MyCases" behavior="loadmore"/>
</interaction>
</interactions>

I probably don’t want to remove these as well.


We have had this issue as well on our pages on version 11.2.10. Removing all the tags that didn’t have any actions on the page has fixed it for that page. Although if there were any page includes on the page loaded (whether they rendered or not) that still had empty tags it blocked the text from being highlighted still.


Hopefully there is a fix soon as we are still building pages and changing them so we will have to constantly check no extra tags are thrown in as we go …


Hello Skuid Community ~

This has been addressed in the new Millau 11.2.12 release which is now available on the Skuid Releases page.

As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes when you upgrade.

Reply