Makes sure geopoint column has room to grow to show entire value. The value is often very close to 250px but this ensures that it can use a bit more if it needs to.
The problem before was a max-width: 500px CSS rule that wasn't getting applied because of change in a different file (submissions/table.vue) that was canceling out the CSS. Using the extra class selector (.table-freeze-scrolling) from the other file worked to have this greater max width go into effect again, and provide a clue to CSS effects from this other file.
We don't add tooltips for field types whose text shouldn't be truncated: int, decimal, date, time, dateTime, and geopoint. (geopoint columns are styled to be up to twice as wide as others.)
What has been done to verify that this works as intended?
Tried it!
Why is this the best possible solution? Were any other approaches considered?
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Does this change require updates to user documentation? If so, please file an issue here and include the link below.
Before submitting this PR, please make sure you have:
[ ] run npm run test and npm run lint and confirmed all checks still pass OR confirm CircleCI build passes
[ ] verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced
Closes https://github.com/getodk/central/issues/635
Makes sure geopoint column has room to grow to show entire value. The value is often very close to 250px but this ensures that it can use a bit more if it needs to.
The problem before was a
max-width: 500pxCSS rule that wasn't getting applied because of change in a different file (submissions/table.vue) that was canceling out the CSS. Using the extra class selector (.table-freeze-scrolling) from the other file worked to have this greater max width go into effect again, and provide a clue to CSS effects from this other file.This PR mentions
What has been done to verify that this works as intended?
Tried it!
Why is this the best possible solution? Were any other approaches considered?
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Does this change require updates to user documentation? If so, please file an issue here and include the link below.
Before submitting this PR, please make sure you have:
npm run testandnpm run lintand confirmed all checks still pass OR confirm CircleCI build passes