Michael Boggs
My feedback
40 results found
-
170 votesMichael Boggs
supported this idea
·
-
69 votesMichael Boggs
supported this idea
·
-
3 votesMichael Boggs
shared this idea
·
-
18 votesMichael Boggs
supported this idea
·
-
3 votesMichael Boggs
supported this idea
·
-
15 votesMichael Boggs
supported this idea
·
-
64 votes
Thank you for your input. This idea is considered for future roadmap. Please reach out to me if you like to share your use case.
Michael Boggs
supported this idea
·
-
16 votesMichael Boggs
supported this idea
·
-
12 votesMichael Boggs
supported this idea
·
-
52 votes
Thank you for the feedback for for highlighting this challenge. This is not currently planned in the near-term, but something we will consider for the future.
Michael Boggs
supported this idea
·
-
39 votes
We have added the origin file's ID, name and path to the COPY event in the events API.
We are considering whether to do the same for the MOVE event.
Michael Boggs
supported this idea
·
-
19 votesMichael Boggs
supported this idea
·
-
49 votes
Thank you for the suggestion. We currently do not have this planned on our roadmap. Please keep the feedback & use cases coming to help us prioritize this in the future!
Michael Boggs
supported this idea
·
-
17 votesMichael Boggs
supported this idea
·
-
7 votes
An error occurred while saving the comment Michael Boggs
shared this idea
·
-
5 votesMichael Boggs
supported this idea
·
-
27 votes
An error occurred while saving the comment Michael Boggs
commented
This is rolling out as part of co-authoring: https://support.box.com/hc/en-us/articles/6321087536787-Box-for-Microsoft-Office-co-authoring-on-desktop-phased-GA-starting
-
72 votes
Not planned as MSFT doesnt have API’s for us to build this integration. Would request all customers to provide feedback to your respective MSFT reps
Michael Boggs
supported this idea
·
-
194 votesMichael Boggs
supported this idea
·
-
9 votesMichael Boggs
supported this idea
·
Just thought I'd add some more information here:
The Box embed widget (located under "more options" when using the ellipse), that generates the "Iframe" code uses the underlying library "Content Preview": https://github.com/box/box-content-preview
This has "autoFocus" set to "True" by default.
This means that when using the "Embed Widget", any page you put the iframe code on will auto scroll to that section of the page. Additionally, there is no option to set "Autofocus" to "false" when generating the iframe code.
I'd like to see an option to set autofocus to false, OR have the autofocus set to false by default in the content preview library.
For reference: The autofocus global attribute is a Boolean attribute indicating that an element should be focused on page load.
Why is this a problem: We often embed documents at the bottom of our intranet pages for reference. When we do this, using the embed widget, the page is automatically scrolling to the location of the iframe, and not to the top of the page, which is what would be desired.