WordPress.org

Making WordPress.org

Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#3350 closed defect (fixed)

bug in docs

Reported by: tazotodua Owned by:
Milestone: Priority: normal
Component: Developer Hub Keywords:
Cc:

Description

visit this page:
https://developer.wordpress.org/themes/customize-api/customizer-objects/
you will see > in code examples, instead of >

Change History (4)

#1 follow-up: @Otto42
2 years ago

  • Resolution set to fixed
  • Status changed from new to closed

I only found one case of that on that page. Replaced it with the correct characters.

Generally speaking, you probably can just mention these cases to the docs team in Slack and somebody there can just edit them directly. Probably no need for a whole ticket on them.

Last edited 2 years ago by Otto42 (previous) (diff)

#2 in reply to: ↑ 1 ; follow-up: @tazotodua
2 years ago

Replying to Otto42:

I only found one case of that on that page. Replaced it with the correct characters.

Generally speaking, you probably can just mention these cases to the docs team in Slack and somebody there can just edit them directly. Probably no need for a whole ticket on them.

1) can you tell me how to mention them? is #accessibility-docs the correct channel ? : https://i.imgur.com/Zbd98BW.png

2) yes, and what you replaced, caused the whole page to replace all occurences. I dont know what happened, but all code examples had > instead of > (other people can approve that, i've opened ticket accidentaly on trac.wordpress and was redirected to here by them). (here screenshot: https://i.imgur.com/5f9Wfdv.png )

Last edited 2 years ago by tazotodua (previous) (diff)

#3 in reply to: ↑ 2 @SergeyBiryukov
2 years ago

  • Component changed from General to Developer Hub

Replying to tazotodua:

1) can you tell me how to mention them? is #accessibility-docs the correct channel ? : https://i.imgur.com/Zbd98BW.png

#docs is the correct channel.

#4 @Otto42
2 years ago

yes, and what you replaced, caused the whole page to replace all occurences. I dont know what happened, but all code examples had > instead

No, it didn't. I checked. I checked again just now, and the display of that page is correct for me. No gt's anywhere.

Note: See TracTickets for help on using tickets.