Open vancromy opened 1 year ago
Hi vancromy! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.
Best regards, Teams Platform
@vancromy - Thanks for reporting your issue. We have tested inline code and multiline code snippets on Microsoft Teams Version 1.6.00.17554 and on Mac OS Ventura 13.4.1, and it was working fine at our end.
After the backtick, please try the below syntax and confirm if it is working or not:
I'm having this issue as well. In-line code snippets doesn't work. Worked OK before my summer vacation (about a month ago). Code blocks (```
) work fine.
You have Microsoft Teams Version 1.6.00.19354. It was last updated on 2023-08-01.
Running macOS 13.5 (22G74). It was broken on macOS 13.4 and 13.4.1 too (and the RSR releases), and might've been broken earlier too.
Historically I've noticed the feature being somewhat shaky too, and in comparison to Slack's similar feature, it's night-and-day. I haven't had a single issue with theirs.
@Nivedipa-MSFT Thanks for the reply. Somehow it is magically working again. As reported by @sidbena I don't seem to be the only one experiencing issues with this feature. I can confirm that I was able to write inline code with [backtick][text][backtick]
yet this exact sequence was not working two days ago. Strange since the Teams version has not changed. So I guess this could be a classic IT Crowd case of just restarting the mac/teams and hoping that fixes it...
@vancromy - Glad to hear that your issue is resolved. Could you please share your valuable feedback via Microsoft Teams Developer Community Response Feedback
@vancromy - We are closing this issue for now. Please feel free to reopen it if required.
Hi vancromy! This issue is closed in our system. We would like your feedback on your experience with our support team and Platform.
Best regards, Teams Platform
@Nivedipa-MSFT Right now I am facing the exact same issue in the Web App. Desktop works fine. I have attached a short video, which demonstrates the broken behavior:
https://github.com/MicrosoftDocs/msteams-docs/assets/15965420/aa167b12-c7dc-4516-8c69-cefab139b5b5
I'm having this exact same problem with both the desktop and web versions.
Backticks don't work anymore.
Unfortunately I can also confirm this issue with the not working single backticks
@Nivedipa-MSFT Can we reopen this issue? I am experiencing the issue again and a few others also seem to be reporting in that the backticks are not always working.
This is still not working. Can we reopen it please?
@vancromy, @kohm - Reopening this issue. We will test this again and update you soon.
@sebastianfrey, @danielsitnik, @jeichhorn, @kohm, @vancromy - After conducting further tests on Mac OS Ventura 13.4.1 and Teams desktop client version 1.6.00.19512-E, we can confirm that it was functioning properly on our end. Kindly refer to the video provided: Please refer the video:
https://github.com/MicrosoftDocs/msteams-docs/assets/92150070/a6315772-ec75-4f60-8706-c41eff5e7fe1
Upon reviewing your provided video, we noticed that for inline code, you missed including the [ after using the backtick. Please consider the following syntax for inline code:
Could you please retest this scenario and provide confirmation?
@Nivedipa-MSFT I am not sure what you mean by I missed [
after using the backtick. As shown in the video you have provided [
and ]
are output in the chat. Furthermore [
and ]
are not an official combination for inline code blocks in Markdown, I guess.
In the official Teams Markdown formatting docs you can find the following quotes:
You can format and share your code on Teams.
To add an inline block of code, start and end the text with a back tick (` ), which is located next to the 1 on your keyboard.
Also note: I am not on Desktop or Mac, I use the web application from https://teams.microsoft.com/. And it still does not work. =/
@Nivedipa-MSFT and everyone else, I found the problem! It is related to the keyboard configuration, when you use a language that has diacritical marks.
I use Brazilian Portuguese, so when I type a backtick `
, the mac highlights it and waits for the next character. If I type an a
, it will replace the whole sequence for the character à
. If I press space, it will leave the backtick there.
However, typing the sequence backtick space my_inline_code backtick space
does not trigger the inline code formatting on Teams. Notice how after I press the backtick, it underlines it and waits for the next character.
https://github.com/MicrosoftDocs/msteams-docs/assets/1395838/ad4ecd53-9fd6-49d3-869e-82e6747ddca3
When I change my keyboard to US English there's no highlighting and waiting for the next character, and the backtick is directly inserted into the text box.
Hi @danielsitnik, Great spot! I am using a Norwegian keyboard setup and have the same issue with the backticks getting highlighted due to diacritical marks. I can confirm that changing to US or even GB International keyboard made inline backticks work again. @Nivedipa-MSFT it seems the inline code feature in MS teams on macs is broken for non US/GB keyboard setttings. Would it be possible to roll-out a fix for all international users? :)
As a follow-up I tested this feature on a Windows VM just now.
OS: Windows 10 Enterprise 21H2 19044.3086 Teams Version: You have Microsoft Teams Version 1.6.00.16472 (64-bit). Citrix HDX Optimized.
NO Keyboard - Keystroke sequence(requires a much more elaborate sequence for inline): [backtick] [t] [e] [s] [t] [backtick] [space] [space]
produces -> tes
(Notice how the last letter t
gets cut off and [space]
needs to be pressed twice to cancel the highlighting of the backtick)
GB Keyboard - Keystroke sequence: [backtick] [t] [e] [s] [t] [backtick] [space]
produces -> test
(This is inline with the MS Teams docs)
So even though the feature works on Windows with both keyboard layouts, the sequence required for a layout which has diacritical marks is not in line with documentation and also truncates the inline code text...
Same Problem for me with a German keyboard on macOS Ventura 13.4 (22F66) and Microsoft Teams Version 1.6.00.19353. I think the problem are the diacritical marks as @danielsitnik already mentioned.
Since I use MS Teams for work as programmer, it would be really helpful, if you could fix this for international keyboard layouts.
And by the way could just have a keyboard shortcut the same way we use it here on GitHub (cmd + e)? This would it make it soo much easier. Thanks! 😊
And then you can use control + space
to change the language and the globe
or fn-key
to get the emojis 😊
https://github.com/MicrosoftDocs/msteams-docs/assets/59373377/6c78ec4f-125f-464c-925e-18fdba3665fb
Same thing happening on a macOS 12.6 and Teams v1.6.00.22155. Changing the keyboard language to US "fixes" the issue but it's not a viable solution.
I have the exact same broken behaviour as the other commentators pointed out in macOS 13.4.1
and Teams 1.6.00.19353
too.
Same error with a different OS/Teams combination: Microsoft Teams, version 1.6.00.22155. macOS 13.5 Also, a non-US keyboard layout.
Tripple backtick+space does work for the code paragraph. Inline code with single backticks does not:
@Nivedipa-MSFT please, any feedback on this?
Same error using the CH keyboard layout for inline code snippet. Multiline snippets work fine.
When switching to US keyboard, inline code snippet work again but it's clearly not possible to use this solution as a long term one.
I have the same issue with Teams running as a web app in Chromium 116.0.5845.96 running on Linux Mint 21.2 with Norwegian keyboard layout.
Same issue on macOS Ventura 13.5 using Microsoft Teams 1.6.00.22155 (last updated on 17/08/23) and keyboard with Brazilian input. The issue is gone when I change the input to US, so I think it is related to the diacritical marks as well.
Please use this link to escalate if you don't get replies.
Just going to leave this here...
Annoying and disappointing that this is still open. It just worked and now its broken for far too long. In an IT team it is just a must have to be able to quickly highlight a code/ command etc. snippet.
@vancromy, @jamilraichouni - Engineering team is working on the fix. Currently we don't have any ETA to share. We will let you know once we get any updates on it.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment.
Why is any author feedback from @vancromy needed? Look like the automation rule to auto-close the ticket because of a lack of author feedback makes no sense here.
Bumping to prevent issue from going stale :)
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment.
Do not "close this issue" until the issue is resolved. This affects Canada's standard layout (CAN/CSA Z243.200).
Also an issue in Teams 1.6.00.24266 on macOS 13.5.2 using a US keyboard layout.
Bumping to prevent issue from going stale :)
Hi, I found a workaround on MacOS :
1) In the Keyboard settings, bind the Show Emoji & Symbols action on the Fn
key
2) In Teams, when writing, hit the Fn
key to show the emoji window, and click the little toggle on the top right to expand the window :
3) Look for the backtick in Punctuation category, and double-click on it to insert it
Those backticks should be processed correctly by Teams
Later, hit Fn
key to toggle the symbols window on/off again (it will stay expanded), then you'll find the backtick directly in the Favourites section.
Hope it will help some of you until this is fixed :-)
Not sure if this helps, but I am using a German Keyboard on MacOS with Microsoft Teams Version 1.6.00.24065. It was last updated on 12.09.23
and I also encounter this issue. I also noticed, that the beautiful colours when copying from my IDE are also gone ☹️
I am facing the same issue : triple backquotes works (not as great as on Slack as we have to do a carriage return before, which is annoying) but single backquote inline code is not working (tested on Swiss German and Swiss French keyboard layout). The fn
"workaround" is not a convenient solution to me, please fix this
I confirm that the issue occurs for
Teams Version 23247.717.2409.7188 (23247.717.2409.7188)
MacOS 13.5.2 (22G91)
Keyboard layout French (AZERTY)
Same here, the Fn solution works but it's super annoying especially for developers and ITs users that are using inline code block every day. Also hard to evangelize Slack/Github/Jira users. It's a pretty common feature elsewhere.
For everyone coming here, it's been 48 days since I first reported the problem being the keyboard layout. 😞
Please use this link to help escalate this issue.
Hello Everyone - Sorry for delay in response. We have informed engineering team about this issue and let you know if we get any inputs.
@vancromy , @danielsitnik - The engineering team is unable to reproduce this issue on their machine using different keyboard layouts. Could you please provide the logs to assist in further investigation?
@vancromy , @danielsitnik - The engineering team is unable to reproduce this issue on their machine using different keyboard layouts. Could you please provide the logs to assist in further investigation?
@Nivedipa-MSFT Did the engineering team perform these tests on a MacOS? With the number of people reporting this issue, I highly doubt it is not reproducible...
Can you let me know how I can generate the logs and I'll happily provide? :)
@vancromy @Nivedipa-MSFT I am on Ubuntu 22.04 and also affected. It seems the bug occurs on all Unix based systems.
Occurring on Windows as well using a uk layout keyboard.
@vancromy - Please reproduce the problem and store the Teams logs. For instructions on storing logs, please refer to the document linked below: Microsoft Teams Log Files
Could you also confirm if you are experiencing this issue on both the Teams web and desktop clients?
The engineering team is unable to reproduce this issue on their machine using different keyboard layouts. Did they test with a non-US keyboard on MacOS? Which keyboard layout did they test? I'm able to reproduce on every Mac (x5) I tested on.
Same problem here with Swiss German keyboard layout on macos 13.4.1 -- using backtick does not trigger the auto-format.
If I switch US keyboard layout, it works as expected.
According to Ukulele (keyboard layout customization utility), the same character is being used for backtick in both SwissGerman and US layouts: U+0060 GRAVE ACCENT
I double-check: If I enter the backtick character while using the US layout, then switch to my layout and paste it, auto-format does not work -- so it's not the character itself.
@vancromy - Please reproduce the problem and store the Teams logs. For instructions on storing logs, please refer to the document linked below: Microsoft Teams Log Files
Could you also confirm if you are experiencing this issue on both the Teams web and desktop clients?
Same problem on the Web. It seems to be an issue when the backtick is used to build accents.
The funny thing is that I can type `some_words` with a keyboard layout containing the issue, and then if I switch to US or GB layout and use the backtick (`) character anywhere afterwards, it will still highlight the some_words
expression written with the bad layout previously.
According to MS teams documentation, inline code snippets can be written by enclosing the code with single backticks as is usually done in markdown.
This
is an example of that implementation.Multiline code snippets do however still work as can be seen in the attached video below.
The keystrokes I pressed in the following video to try and write an inline code snippet was
[backtick]my code[backtick][space]
In my current version of Teams this does not work (see: https://github.com/MicrosoftDocs/msteams-docs/assets/59556820/8b90f413-9adf-466d-9df6-b596bc2d7d4c).
Teams version:
You have Microsoft Teams Version 1.6.00.17554. It was last updated on 31/07/2023.
OS Info: macOS 13.4.1 (c) (22F770820d)EDIT: It seems someone opened a FR for this around the same time I opened this issue. Feel free to upvote that one too: https://feedbackportal.microsoft.com/feedback/idea/965f520a-e40c-ee11-a81c-000d3a7a48db