This is issue occurring again and again. This is reference to recently closed issue which is related. https://github.com/SharePoint/sp-dev-docs/issues/3537
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
it's back again, that was a "short" working fix ;(
Same issue - it is back again - https://github.com/SharePoint/sp-dev-docs/issues/3537
Yesterday :
Today:
Additionally the column header is not not hiding
{ "hideListHeader": true, "hideSelection": true, "hideColumnHeader":true "rowFormatter": { "elmType": "div", "attributes": { "class": "ms-bgColor-white ms-borderColor-themePrimary--hover" }, "style": { "margin": "0px 0", "padding": "3PX", "border": "none", "cursor": "pointer", "float": "left" }, "children": [ { "elmType": "a", "attributes": { "href": "[$Link]", "target": "_blank" }, "style": { "width": "100%", "background-color": "transparent", "display": "inline-flex", "text-decoration": "none" }, "children": [ { "elmType": "div", "attributes": { "class": "ms-borderColor-themePrimary ms-bgColor-neutralLighter" }, "style": { "min-width": "75px", "display": "flex", "border-width": "1px", "border-style": "solid", "box-sizing": "border-box", "align-items": "center" }, "children": [ { "elmType": "div", "attributes": { "iconName": "Link12", "class": "ms-fontSize-32 ms-fontWeight-regular ms-fontColor-black" }, "style": { "flex": "none", "padding-top": "13px", "padding-left": "22px", "height": "30px", "font-size": "28px", "padding-bottom": "9px" } } ] }, { "elmType": "div", "attributes": { "class": "ms-fontColor-themePrimary ms-borderColor-themePrimary ms-fontSize-m" }, "style": { "border-width": "1px", "border-style": "solid", "box-sizing": "border-box", "width": "300px", "text-align": "left", "HEIGHT": "28PX", "color": "black", "overflow": "hidden", "padding-left": "10px", "padding-top": "6px" }, "children": [ { "elmType": "div", "txtContent": "[$Link.desc]", "style": { "height": "24px" }, "attributes": { "title": "[$Link.desc]" } } ] } ] } ] } }
@andrewconnell - it is related to list-formatting area , This is a previously opened issue that was closed (https://github.com/SharePoint/sp-dev-list-formatting/issues/204) but it is still an issue and needs to be tracked/fixed by the team
@PrasadKasireddy thanks... it doesn't help when all the default sections were removed from this issue when it was submitted making it unclear what this is (bug/question/discussion/etc).
@andrewconnell thanks... it doesn't help when all the default sections were removed from this issue when it was submitted making it unclear what this is (bug/question/discussion/etc).
https://github.com/SharePoint/sp-dev-list-formatting/issues/123
This is where it started.It was fixed before
@PrasadKasireddy thanks... it doesn't help when all the default sections were removed from this issue when it was submitted making it unclear what this is (bug/question/discussion/etc).
Hello @andrewconnell , I have submitted this issue from my mobile. That is why I couldn't type properly.
But this is not a completely new issue. This issue occured in last year and few days ago too.
The reference issue from the past I have added gives clear information.
I think this issue should be given high priority as the earlier fix is not working and team might know the route cause already. Our users are loosing confidence on SharePoint design due to this.
The issue seems to be fixed now. Can any one from Microsoft support team confirm that a permanent fix is applied before closing this? Or Should we wait and see for stability?
Yes confirmed....fixed...
The issue seems to be fixed now. Can any one from Microsoft support team confirm that a permanent fix is applied before closing this? Or Should we wait and see for stability?
Agree @asifahmeds as it issue is not stable, it was happen yesterday as well. it is happening intermittently.
seems to work again (for now) hope it keeps working.
As you say it's working, there's nothing to investigate... thus closing. Feel free to open a new issue if it happens again.
@all - In the future, please consider the following points. These things make it easier to help (1) identify, (2) triage, (3) research, and (4) troubleshoot if there is a real error going on.
As @VesaJuvonen commented in the other issue https://github.com/SharePoint/sp-dev-docs/issues/3537#issuecomment-577335878, the more detail, formatting code, etc you can provide, the easier it is to help. But that was never shared in the referenced issue nor has it been fully included in this one either.
@harshdamaniahd above in your reply, https://github.com/SharePoint/sp-dev-docs/issues/5213#issuecomment-578058323, you have a blob of JSON... please refer to our wiki page on How to create a good issue: Use code formatting (inline & blocks) on how to properly format the JSON. As you pasted it, it's near impossible to read.
@asifahmeds said:
I have submitted this issue from my mobile. That is why I couldn't type properly.
Understood, but that doesn't change the fact that without that detail, not enough detail/context was shared making it near impossible to move forward on this.
Issue is back again :( . I don't understand why no celar information is being given about this issue.
@harshdamaniahd - Is this issue back again today please confirm.
@harshdamaniahd - Is this issue back again today please confirm.
Yes.
This issue has appeared on my tenant.
Confirm, issue is back.
Related issue with simple reproduction steps
@FredrikEkstroem https://github.com/SharePoint/sp-dev-docs/wiki/Issue-List#our-approach-to-closed-issues
@FredrikEkstroem https://github.com/SharePoint/sp-dev-docs/wiki/Issue-List#our-approach-to-closed-issues
That's all very well, but this issue has had multiple posts, all getting prematurely closed. Perhaps leave the dust to settle so that people can confirm it's been fixed for more than a day before troubles appear again?
@andrewconnell Let me clear the air, the header issue is still reproducible on my tenant. Please guide team to fix it.
@Divyeshkotadia https://github.com/SharePoint/sp-dev-docs/wiki/Issue-List#our-approach-to-closed-issues
Looks like there is a fix coming in 2-3 weeks #5251
Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues